CVE-2017-5064
UnknownEPSS 1.37%
Last modified
CVE-2017-5064 is a vulnerability of currently unknown severity. Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.. EPSS estimates a 1.37% chance of exploitation in the next 30 days.
Description
Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | < 58.0.3029.81 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-5064?
Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
How severe is CVE-2017-5064?
Severity scoring for CVE-2017-5064 is pending analysis. The EPSS model estimates a 1.37% probability of exploitation in the next 30 days.
How do I fix CVE-2017-5064?
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 2017
- CVE-2017-5058A use after free in PrintPreview in Google Chrome prior to 5…
- CVE-2017-5059Type confusion in Blink in Google Chrome prior to 58.0.3029.…8.8
- CVE-2017-5060Insufficient Policy Enforcement in Omnibox in Google Chrome …6.5
- CVE-2017-5061A race condition in navigation in Google Chrome prior to 58.…5.3
- CVE-2017-5062A use after free in Chrome Apps in Google Chrome prior to 58…8.8
- CVE-2017-5063A numeric overflow in Skia in Google Chrome prior to 58.0.30…8.8
- CVE-2017-5065Lack of an appropriate action on page navigation in Blink in…4.7
- CVE-2017-5066Insufficient consistency checks in signature handling in the…6.5
- CVE-2017-5067An insufficient watchdog timer in navigation in Google Chrom…6.5
- CVE-2017-5068Incorrect handling of picture ID in WebRTC in Google Chrome …7.5
- CVE-2017-5069Incorrect MIME type of XSS-Protection reports in Blink in Go…6.1
- CVE-2017-5070Type confusion in V8 in Google Chrome prior to 59.0.3071.86 …8.8
Are you affected by CVE-2017-5064?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST