CVE-2017-5030 — Chrome
HIGHCVE-2017-5030 is a high-severity (CVSS 8.8) Out-of-bounds Read vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-06-08) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.2987.108 for Android allowed a remote attacker to execute arbitrary…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-06-08. Federal agencies were required to remediate by 2022-06-22.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-5030.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2017-5030 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,415 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Description
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.2987.108 for Android allowed a remote attacker to execute arbitrary code via a crafted HTML page.
Affected Products
debian linuxdebianchromegoogleenterprise linux desktopredhatenterprise linux serverredhatenterprise linux workstationredhatResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Incorrect handling of complex species in V8 in Google Chrome prior to 57…
Incorrect handling of complex species in V8 in Google Chrome prior to 57…
Incorrect handling of complex species in V8 in Google Chrome prior to 57…
Incorrect handling of complex species in V8 in Google Chrome prior to 57…
Detection & mitigation playbook
VulnerabilityDetect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2017-5030 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 6 Supplementary | chromium-browser-0:57.0.2987.98-1.el6 | RHSA-2017:0499 |
Frequently Asked Questions
Is CVE-2017-5030 in your dependencies?
Find it across , including transitive dependencies.