CVE-2017-5030
Exploitation confirmed. First attested on 2022-06-08 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2017-04-24
- WeaknessCWE-125
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTCObserved activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-5030?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-5030?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 8.0 | = 8.0 | no fix published | NVD |
| 9.0 | = 9.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 57.0 | < 57.0.2987.108 | 57.0.2987.108 | NVD |
| 57.0 | < 57.0.2987.98 | 57.0.2987.98 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 6.0 | = 6.0 | no fix published | NVD |
2 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- CISA’s required action: Apply updates per vendor instructions.due 2022-06-22
Advisories and patches
- chromereleases.googleblog.comRelease Notes · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
CISA Known Exploited Vulnerability
- Date Added
- 2022-06-08
- Patch Due Date
- 2022-06-22
- Ransomware Use
- Unknown
- Required Action
- Apply updates per vendor instructions.
Sources
- CISA KEVKEV entry2022-06-08
- GCVEexploitation2022-06-08
- CISA-ADPSSVC decisionactive2025-01-29
- OpenCVESSVC decisionactive—
- CISA-ADPCVSS 3.18.82025-01-29
- NVDCVSS 3.18.8read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- CISA-ADPweakness (CWE)CWE-1252025-01-29
- NVDweakness (CWE)CWE-125read 2026-10-23
- FIRST EPSSEPSS score40.6 %read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2017-04-24
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2017-5030?
Is CVE-2017-5030 actively exploited?
What is the CVSS score for CVE-2017-5030?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.