CVE-2016-5198
Google Chromium V8 Out-of-Bounds Memory
- Published19 Jan 2017
- Added to CISA KEV8 Jun 2022
- Remediation due22 Jun 2022
Description
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac included incorrect optimisation assumptions, which allowed a remote attacker to perform arbitrary read/write operations, leading to code execution, 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
- http://rhn.redhat.com/errata/RHSA-2016-2672.html
- https://chromereleases.googleblog.com/2016/11/stable-channel-update-for-desktop.html
- https://crbug.com/659475
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2016-5198
- http://www.securityfocus.com/bid/94079
- http://www.securitytracker.com/id/1037224
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2016-5198 being actively exploited?
Yes. CVE-2016-5198 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 8 Jun 2022.
How severe is CVE-2016-5198?
CVE-2016-5198 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 34.2% probability of exploitation.
Which products are affected by CVE-2016-5198?
Affected products include Google Chrome, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Server, Redhat Enterprise Linux Workstation.
How do I fix CVE-2016-5198?
Upgrade affected software to a fixed version, for example Google Chrome 54.0.2840.85 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2016-5198 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.