Heap overflow via mismatched restoration worker count
Published Dec 27, 2023 · Updated Jun 23, 2026
Heap-based buffer overflow in Alliance for Open Media libaom before 3.7.1 allows attackers to corrupt memory via frame resizing. av1_loop_restoration_dealloc() uses the current worker count instead of the count stored with the allocated loop-restoration worker array, so its cleanup loop can walk beyond that allocation. The condition requires a multithreaded encode that increases frame resolution; the overflow reads adjacent memory or terminates the encoding process.
Summary
What happened
Heap-based buffer overflow in Alliance for Open Media libaom before 3.7.1 allows attackers to corrupt memory via frame resizing. av1_loop_restoration_dealloc() uses the current worker count instead of the count stored with the allocated loop-restoration worker array, so its cleanup loop can walk beyond that allocation. The condition requires a multithreaded encode that increases frame resolution; the overflow reads adjacent memory or terminates the encoding process.
The record
- CVE
- CVE-2023-6879
- Published
- Dec 27, 2023
- Updated
- Jun 23, 2026
- Vendor
- Alliance for Open Media
- Product
- libaom
- Classifications
- CWE-787, CWE-20, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 27, 2023CVE publishedPublication date reported by the CVE source.
- Jun 23, 2026Record 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=0 <3.7.1
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.
Weakness, pattern, technique
Public exploit references
- Upstream ResizeSimpleTest reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
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