Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2023-5217

Google Chromium libvpx Heap Buffer Overflow Vulnerability

Google Chromium libvpx

Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CVSS
8.8
HIGH
EPSS
49%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
28 Sep 2023
CWE-787

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 2 October 2023. US federal agencies were required to remediate it by 23 October 2023.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 49%, which is higher than 98.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2023-5217 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2023-5217.

What does CVE-2023-5217 affect?

CVE-2023-5217 affects Google Chromium libvpx. Heap buffer overflow in vp8 encoding in libvpx in Google Chrome prior to 117.0.5938.132 and libvpx 1.13.1 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

How severe is CVE-2023-5217?

CVE-2023-5217 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 49%, higher than 98.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 23 October 2023.

How should organisations respond to CVE-2023-5217?

Apply the vendor patch for Google Chromium libvpx as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.