Code execution via installer DLL search order
Published Apr 21, 2020 · Updated Aug 4, 2024
DLL search-order hijacking in the Google Earth Pro Windows installer before 7.3.3 allows local users to execute arbitrary code. The executable installer searches an uncontrolled local path and loads an attacker-placed DLL before the intended library; Google has not identified the DLL. Exploitation requires a user to launch the installer after the malicious file is placed in a searched location, and the code runs with the installer's privileges.
Summary
What happened
DLL search-order hijacking in the Google Earth Pro Windows installer before 7.3.3 allows local users to execute arbitrary code. The executable installer searches an uncontrolled local path and loads an attacker-placed DLL before the intended library; Google has not identified the DLL. Exploitation requires a user to launch the installer after the malicious file is placed in a searched location, and the code runs with the installer's privileges.
The record
- CVE
- CVE-2020-8895
- Published
- Apr 21, 2020
- Updated
- Aug 4, 2024
- Vendor
- Product
- Google Earth Pro
- Classifications
- CWE-427, CWE-426, T1574.001
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <7.3.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo