CVE-2018-17480
Google Chromium V8 Out-of-Bounds Write
- Published11 Dec 2018
- Added to CISA KEV8 Jun 2022
- Remediation due22 Jun 2022
Description
Execution of user supplied Javascript during array deserialization leading to an out of bounds write in V8 in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2018:3803
- https://chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html
- https://crbug.com/905940
- https://security.gentoo.org/glsa/201908-18
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2018-17480
- https://www.debian.org/security/2018/dsa-4352
- http://www.securityfocus.com/bid/106084
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2018-17480 being actively exploited?
Yes. CVE-2018-17480 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 8 Jun 2022.
How severe is CVE-2018-17480?
CVE-2018-17480 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 35.6% probability of exploitation.
Which products are affected by CVE-2018-17480?
Affected products include Google Chrome, Debian Linux, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.
How do I fix CVE-2018-17480?
Upgrade affected software to a fixed version, for example Google Chrome 71.0.3578.80 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2018-17480 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, Secuno flags any affected asset as top-priority automatically. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.