CVE-2017-5030

Exp

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.

Published: 2017-04-24 Last update: 2026-04-21 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-5030 is rated Critical Active Threat (94.1/100): CVSS High severity, with high exploitation likelihood (EPSS 50.31%, 98th percentile). CISA KEV confirms active exploitation (added 2022-06-08) affecting Google / Chromium V8. a weakness (CWE-125) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2017-5030

Name: Google Chromium V8 Memory Corruption Vulnerability · CISA KEV detail

Exploit added: 2022-06-08

Action due: 2022-06-22

Required action: Apply updates per vendor instructions.

Public exploit references (Exploit-DB) for CVE-2017-5030

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2017-5030

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-22 50.65% 50.31% -0.34%
2 2026-01-14 48.21% 50.65% +2.44%
3 2026-01-13 — 48.21% —

Full EPSS history (29 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-5030

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-5030

OS Trackers for CVE-2017-5030

vendor priority summary link
gentoo normal CVE-2017-5030: 1 GLSA(s) (201704-02), 1 atom(s) (www-client/chromium); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-5030
redhat high — https://access.redhat.com/security/cve/CVE-2017-5030
ubuntu medium CVE-2017-5030 medium priority: Ubuntu including 4 source packages (chromium-browser, libv8, libv8-3.14, oxide-qt), 36 status rows across 9 suites (artful, bionic, cosmic, precise, trusty, upstream, xenial, yakkety, zesty): released 14, DNE 12, ignored 8, needed 2. https://ubuntu.com/security/CVE-2017-5030

Affected software / configurations for CVE-2017-5030

Vendor Product Version Raw CPE
google chrome < 57.0.2987.98 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
google chrome < 57.0.2987.108 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
debian debian_linux 8.0 cpe:2.3:o:debian:debian_linux:8.0:*:*:*:*:*:*:*
debian debian_linux 9.0 cpe:2.3:o:debian:debian_linux:9.0:*:*:*:*:*:*:*
redhat enterprise_linux_desktop 6.0 cpe:2.3:o:redhat:enterprise_linux_desktop:6.0:*:*:*:*:*:*:*
redhat enterprise_linux_server 6.0 cpe:2.3:o:redhat:enterprise_linux_server:6.0:*:*:*:*:*:*:*
redhat enterprise_linux_workstation 6.0 cpe:2.3:o:redhat:enterprise_linux_workstation:6.0:*:*:*:*:*:*:*

References for CVE-2017-5030

cvelogic Threat Intelligence