CVE-2023-5217 Google Chromium libvpx: memory-safety flaw
In plain words: The program mishandles the memory it uses to keep track of data. A specially made input can scramble that memory. Usually lets an attacker crash the program or run their own code with its permissions.
Confirmed exploited by CISA on · US federal patch deadline Oct 23, 2023
What to do
- Install Google's security update for Chromium libvpx. If no update exists, follow the vendor's workaround or stop using the product until one ships.
- Let the browser auto-update and relaunch it when it asks — the fix is not active until you do.
- Keep extensions to a minimum and remove ones you do not recognise.
- Stop using Internet Explorer and any browser that no longer gets updates.
Who is affected
Could reach you. This one is aimed at devices or apps of the kind people own.
What's at risk: A malicious or hacked website can be enough. Browser bugs are often the first step in a longer attack on the whole computer or phone.
The details
- Official name
- Google Chromium libvpx Heap Buffer Overflow Vulnerability
- Product
- Google Chromium libvpx
- CISA description
- Google Chromium libvpx contains a heap buffer overflow vulnerability in vp8 encoding that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could impact web browsers using libvpx, including but not limited to Google Chrome.
- Type of flaw
- Memory-safety flaw (CWE-787)
- Confirmed exploited
- Oct 2, 2023
- US federal patch deadline
- Oct 23, 2023
Ask Cleus about it
Ask about a vulnerability, an update, a weird message, or the news. Plain-word answers, free, no account.
Answering about CVE-2023-5217 ·
Questions about CVE-2023-5217
Is CVE-2023-5217 being exploited?
Yes. CISA added CVE-2023-5217 to its Known Exploited Vulnerabilities catalog on Oct 2, 2023, which means there is reliable evidence of real-world attacks.
How do I fix CVE-2023-5217?
Install Google's security update for Chromium libvpx. If no update exists, follow the vendor's workaround or stop using the product until one ships. Let the browser auto-update and relaunch it when it asks — the fix is not active until you do.
Am I affected by CVE-2023-5217?
Only if you use Google Chromium libvpx. This one is aimed at devices or apps of the kind people own.