CVE-2020-6417
HIGHCVSS 7.8/10EPSS 0.29%
Last modified
CVE-2020-6417 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. Inappropriate implementation in installer in Google Chrome prior to 80.0.3987.87 allowed a local attacker to execute arbitrary code via a crafted registry entry.. EPSS estimates a 0.29% chance of exploitation in the next 30 days.
Description
Inappropriate implementation in installer in Google Chrome prior to 80.0.3987.87 allowed a local attacker to execute arbitrary code via a crafted registry entry.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 80.0.3987.87 |
References
- http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00015.htmlThird Party Advisory
- https://crbug.com/1033824Permissions Required
- http://lists.opensuse.org/opensuse-security-announce/2020-02/msg00015.htmlThird Party Advisory
- https://crbug.com/1033824Permissions Required
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-6417?
Inappropriate implementation in installer in Google Chrome prior to 80.0.3987.87 allowed a local attacker to execute arbitrary code via a crafted registry entry.
How severe is CVE-2020-6417?
CVE-2020-6417 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.29% probability of exploitation in the next 30 days.
How do I fix CVE-2020-6417?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-6411Insufficient validation of untrusted input in Omnibox in Goo…5.4
- CVE-2020-6412Insufficient validation of untrusted input in Omnibox in Goo…5.4
- CVE-2020-6413Inappropriate implementation in Blink in Google Chrome prior…8.8
- CVE-2020-6414Insufficient policy enforcement in Safe Browsing in Google C…8.8
- CVE-2020-6415Inappropriate implementation in JavaScript in Google Chrome …8.8
- CVE-2020-6416Insufficient data validation in streams in Google Chrome pri…8.8
- CVE-2020-6418Type confusion in V8 in Google Chrome prior to 80.0.3987.122…8.8
- CVE-2020-6419Out of bounds write in V8 in Google Chrome prior to 81.0.404…8.8
- CVE-2020-6420Insufficient policy enforcement in media in Google Chrome pr…8.8
- CVE-2020-6422Use after free in WebGL in Google Chrome prior to 80.0.3987.…8.8
- CVE-2020-6423Use after free in audio in Google Chrome prior to 81.0.4044.…8.8
- CVE-2020-6424Use after free in media in Google Chrome prior to 80.0.3987.…8.8
Are you affected by CVE-2020-6417?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST