Local code execution via crafted registry entry
Published Feb 11, 2020 · Updated Aug 4, 2024
Improper handling in Google Chrome's Windows installer before 80.0.3987.87 allows local users to execute arbitrary code via a crafted registry entry. Google identifies the installer as the affected component but has not publicly disclosed which registry value is trusted or the incorrect operation performed with it. Exploitation requires local access and control of the crafted registry entry, and successful exploitation runs attacker-controlled code in the installer's execution context.
Summary
What happened
Improper handling in Google Chrome's Windows installer before 80.0.3987.87 allows local users to execute arbitrary code via a crafted registry entry. Google identifies the installer as the affected component but has not publicly disclosed which registry value is trusted or the incorrect operation performed with it. Exploitation requires local access and control of the crafted registry entry, and successful exploitation runs attacker-controlled code in the installer's execution context.
The record
- CVE
- CVE-2020-6417
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- T1112
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 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 <80.0.3987.87
What conditions does exploitation require?
What is affected?
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