CyberSecBulletin
CVE-2023-5217Exploited in the wildNVD status: Analyzed

Google Chromium libvpx Heap Buffer Overflow

Published Updated By the CyberSecBulletin desk

CVE-2023-5217 is a high-severity out-of-bounds write vulnerability in Chrome from Google, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 117.0.5938.132 as the first without the flaw, so updating Chrome to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on October 2, 2023, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Chrome to 117.0.5938.132 or a later version.
  2. Update libvpx to 1.13.1 or a later version.
  3. Update Firefox to 115.3.1 or 118.0.1 or 118.1, whichever matches your release line, or a later version.
  4. CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
  5. Read the advisory on chromereleases.googleblog.com for workarounds and exact fixed builds.
  6. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  7. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
GoogleChrome117.0.5938.132 up to, but not including, 117.0.5938.132117.0.5938.132
Googlelibvpx1.13.1 up to, but not including, 1.13.11.13.1
MicrosoftEdge116.0.1938.98; 117.0.2045.47Not stated
MicrosoftEdge Chromium116.0.5845.229; 117.0.5938.132Not stated
MozillaFirefoxbefore 115.3.1; before 118.0.1; before 118.1115.3.1, 118.0.1, 118.1
MozillaThunderbirdbefore 115.3.1115.3.1
Fedora ProjectFedora37; 38; 39Not stated
DebianDebian Linux10.0; 11.0; 12.0Not stated
AppleiPadOS17.0 up to, but not including, 17.0.3; 16.717.0.3
AppleIphone OS17.0 up to, but not including, 17.0.3; 16.717.0.3
Red HatEnterprise Linux9.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.8HighNVD
CVSS 3.18.8HighCISA (ADP)

Official description

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)

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. Added to CISA's Known Exploited Vulnerabilities catalogue.
  3. Deadline for US federal agencies to remediate, set by CISA.
  4. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  5. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Technical write-ups (may include proof of concept)

Other references

Other vulnerabilities in Chrome

All Chrome vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.