dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 23 Oct 2023.
FirefoxWeb browser · Mozilla

CVE-2023-5217

HIGH · 8.8 CVSS v3.1 Published 2023-09-28
Fix available
A fix is available. Upgrade to 1.13.1 / 115.3.1 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit Remotely reachable No privileges Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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)

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Heap buffer overflow vulnerability in the vp8 encoding component of libvpx allows a remote attacker to trigger heap corruption via a specially crafted HTML page containing malicious video content, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 117.0.5938.132 or later, and update libvpx to version 1.13.1 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FirefoxWeb browser
Affected:< 115.3.1< 118.0.1< 118.1
FedoraOperating system
Affected:= 37= 38= 39
Debian LinuxOperating system
Affected:= 10.0= 11.0= 12.0
ChromeWeb browser
Affected:< 117.0.5938.132
Enterprise LinuxOperating system
Affected:= 9.0
LibvpxApplication
Affected:< 1.13.1
EdgeWeb browser
Affected:= 116.0.1938.98= 117.0.2045.47
Edge ChromiumWeb browser
Affected:= 116.0.5845.229= 117.0.5938.132

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed browser or application using libvpx
    Check system for Firefox, Chrome, Edge, or any application that links to libvpx library. On Linux: 'dpkg -l | grep -E "firefox|chromium|edge"' or 'rpm -qa | grep -E "firefox|chromium|edge"'. On Windows: Check installed programs or browser about dialog.
    Affected if Any of the affected browsers (Firefox < 115.3.1, < 118.0.1, or < 118.1; Chrome < 117.0.5938.132; Edge versions 116.0.1938.98, 117.0.2045.47, 116.0.5845.229, 117.0.5938.132) are installed.
  2. Determine Firefox version
    For Firefox: Navigate to 'about:support' or run 'firefox --version' from command line.
    Affected if Version is lower than 115.3.1, or falls between 118.0 and 118.0.1, or is below 118.1.
  3. Determine Chrome or Chromium-based Edge version
    For Chrome: Navigate to 'chrome://version' or run 'google-chrome --version'. For Edge: Navigate to 'edge://version' or run 'msedge --version'.
    Affected if Chrome version is below 117.0.5938.132. For Edge, version matches 116.0.1938.98, 117.0.2045.47, 116.0.5845.229, or 117.0.5938.132.
  4. Check libvpx library version directly
    If using libvpx directly: run 'pkg-config --modversion vpx' or check the shared library file 'libvpx.so' with 'objdump -p libvpx.so | grep VERSION' or check file metadata.
    Affected if libvpx version is below 1.13.1.
  5. Verify vp8 encoding capability is accessible
    The vulnerability exists in the vp8 encoder component. Check if the application has vp8 encoding enabled or if vp8 video files are processed. This may be observed in browser media settings, encoder configurations, or by inspecting media handling logs.
    Affected if The vp8 encoder feature is enabled or the application processes vp8 encoded content.

You are affected if you have any of the listed browser versions installed (Firefox < 115.3.1, < 118.0.1, or < 118.1; Chrome < 117.0.5938.132; specific Edge versions) or libvpx < 1.13.1, and the vp8 encoder functionality is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.13.1 / 115.3.1 / 117.0.5938.132 or later
Fixed in 1.13.1115.3.1117.0.5938.132
Vendor patch www.openwall.com →
Interim mitigation

Update Google Chrome to version 117.0.5938.132 or later, and update libvpx to version 1.13.1 or later to remediate this vulnerability.

Recommended fix High confidence

libvpx 1.13.1 or later; Chrome/Chromium 117.0.5938.132+; Firefox 118.1+ (or 115.3.1/118.0.1)

  1. For Chrome/Chromium-based browsers: Upgrade to Chrome 117.0.5938.132 or later, or Chrome 118.x when available
  2. For Firefox: Upgrade to Firefox 115.3.1, 118.0.1, 118.1 or later (whichever is available for your OS)
  3. For Edge: Upgrade to version 117.0.2045.47 or later
  4. For Linux distributions (Fedora, Debian, Enterprise Linux): Update the libvpx package to version 1.13.1 or later via your package manager (e.g., dnf update libvpx or apt update && apt upgrade libvpx)
  5. Verify the fix by checking the libvpx version (vp8 -h or vpxenc --version) shows 1.13.1 or later
  6. Restart all browsers after updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-5217 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data