Content-process heap corruption via thread-count reconfiguration
Published Sep 28, 2023 · Updated Oct 21, 2025
Heap buffer overflow in libvpx before 1.13.1 and Chrome before 117.0.5938.132 allows remote attackers to corrupt heap memory via VP8 media. The VP8 encoder's vp8_change_config function accepts a post-initialization thread-mode change even though thread-dependent buffers are allocated only when the compressor is created. A victim must load attacker-controlled VP8 media; the resulting allocation mismatch can corrupt or crash the sandboxed content process.
Summary
What happened
Heap buffer overflow in libvpx before 1.13.1 and Chrome before 117.0.5938.132 allows remote attackers to corrupt heap memory via VP8 media. The VP8 encoder's vp8_change_config function accepts a post-initialization thread-mode change even though thread-dependent buffers are allocated only when the compressor is created. A victim must load attacker-controlled VP8 media; the resulting allocation mismatch can corrupt or crash the sandboxed content process.
The record
- CVE
- CVE-2023-5217
- Published
- Sep 28, 2023
- Updated
- Oct 21, 2025
- Vendor
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2023CVE publishedPublication date reported by the CVE source.
- Oct 21, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=117.0.5938.132 <117.0.5938.132
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Reported exploitation
- CISA Known Exploited Vulnerabilities catalog entryknown exploited catalog
- Google-reported in-the-wild exploitationreported exploitation
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo