Tool crash via out-of-bounds slice-data read
Published Oct 26, 2022 · Updated Apr 14, 2025
Heap-buffer over-read in Axiomatic Systems Bento4 avcinfo 1.6.0-639 allows attackers to crash the tool via a crafted AVC file. AP4_BitStream::WriteBytes reads eight bytes from slice data after avcinfo accepts a NAL unit with only one payload byte. Processing a supplied file with avcinfo is required; the published proof of concept demonstrates an AddressSanitizer abort but does not establish code execution.
Summary
What happened
Heap-buffer over-read in Axiomatic Systems Bento4 avcinfo 1.6.0-639 allows attackers to crash the tool via a crafted AVC file. AP4_BitStream::WriteBytes reads eight bytes from slice data after avcinfo accepts a NAL unit with only one payload byte. Processing a supplied file with avcinfo is required; the published proof of concept demonstrates an AddressSanitizer abort but does not establish code execution.
The record
- CVE
- CVE-2022-3664
- Published
- Oct 26, 2022
- Updated
- Apr 14, 2025
- Vendor
- Axiomatic Systems LLC
- Product
- Bento4
- Classifications
- CWE-787, CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 26, 2022CVE publishedPublication date reported by the CVE source.
- Apr 14, 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=n/a
What conditions does exploitation require?
What is affected?
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
- avcinfo_poc1.zipproof 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