CVE-2023-5217: Google Chromium libvpx Heap Buffer Overflow
Google Chromium libvpx · listed in the CISA catalog of actively exploited vulnerabilities since 2023-10-02.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 49%
- higher than 98.9% of all CVEs
- Added to CISA KEV
- 2023-10-02
- US federal due date 2023-10-23
- Ubuntu priority
- high
What is CVE-2023-5217?
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)
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 117.0.5938.132
- 117.0.5938.132
- Google libvpxAffectedFixed in
- < 1.13.1
- 1.13.1
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
| Google libvpx |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 24.04 LTS·mozjs102
Status: no fixed version published · Ubuntu tracker
Ubuntu 24.04 LTS·thunderbird
Fixed: 1:115.3.1+build1-0ubuntu1
Ubuntu 22.04 LTS·libvpx
Fixed: 1.11.0-2ubuntu2.2
Ubuntu 22.04 LTS·mozjs102
Status: no fixed version published · Ubuntu tracker
Ubuntu 22.04 LTS·mozjs78
Status: no fixed version published · Ubuntu tracker
Ubuntu 22.04 LTS·mozjs91
Status: no fixed version published · Ubuntu tracker
Ubuntu 22.04 LTS·thunderbird
Fixed: 1:115.3.1+build1-0ubuntu0.22.04.2
Ubuntu 20.04 LTS·firefox
Fixed: 118.0.1+build1-0ubuntu0.20.04.1
Ubuntu 20.04 LTS·libvpx
Fixed: 1.8.2-1ubuntu0.2
Ubuntu 20.04 LTS·mozjs52
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·mozjs68
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·thunderbird
Fixed: 1:115.3.1+build1-0ubuntu0.20.04.1
Ubuntu 18.04 LTS·mozjs38
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·mozjs52
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·libvpx
fix via Ubuntu Pro
Fixed: 1.7.0-3ubuntu0.18.04.1+esm1
Ubuntu 16.04 LTS·libvpx
fix via Ubuntu Pro
Fixed: 1.5.0-2ubuntu1.1+esm2
Ubuntu 14.04 LTS·libvpx
fix via Ubuntu Pro
Fixed: 1.3.0-2ubuntu0.1~esm3
Debian 14 (forky)·firefox-esr
testing distribution
Status: Debian: minor issue, no fix planned
Debian 13 (trixie)·firefox-esr
Status: Debian: minor issue, no fix planned
Debian 12 (bookworm)·chromium
Fixed: 117.0.5938.132-1~deb12u1
Debian 12 (bookworm)·firefox-esr
Status: Debian: minor issue, no fix planned
Debian 12 (bookworm)·libvpx
Fixed: 1.12.0-1+deb12u1
Debian 12 (bookworm)·thunderbird
Fixed: 1:115.3.1-1~deb12u1
Check and fix on a server
Run on each Ubuntu or Debian server. Replace libvpx with the source package from the table above (this CVE affects 11 source packages).
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="libvpx"'2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="libvpx"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
No fixed version yet on 2 releases
Debian 14 (forky), Debian 13 (trixie): no fixed version of the affected packages yet, so every installed version there is affected. Until a fix is published:
- Follow the vendor's advisory for a mitigation or patch: chromereleases.googleblog.com/2023/09/stable-channel-upda…
- If the server does not need the package, remove it, or replace it with a maintained alternative.
- Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.
This page updates automatically when Ubuntu or Debian publish a fix.
Rows marked “fix via Ubuntu Pro”: these fixes are only installable with an Ubuntu Pro subscription (ESM). Attach the machine first (sudo pro attach, then sudo pro enable esm-infra esm-apps), then run the commands above.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-787 Out-of-bounds Write
References
Other advisories
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.