Utility crash via unchecked four-byte tag read
Published Oct 3, 2022 · Updated Aug 3, 2024
Heap-buffer over-read in Bento4 mp4tag 1.6.0-639 allows local users to crash the utility via a one-character removal tag. AP4_Atom::TypeFromString unconditionally reads four bytes from the supplied tag name, so a one-character value overruns its two-byte heap allocation. The demonstrated trigger requires a local mp4tag invocation with --remove and aborts an AddressSanitizer build, so no network service impact is established.
Summary
What happened
Heap-buffer over-read in Bento4 mp4tag 1.6.0-639 allows local users to crash the utility via a one-character removal tag. AP4_Atom::TypeFromString unconditionally reads four bytes from the supplied tag name, so a one-character value overruns its two-byte heap allocation. The demonstrated trigger requires a local mp4tag invocation with --remove and aborts an AddressSanitizer build, so no network service impact is established.
The record
- CVE
- CVE-2022-41429
- Published
- Oct 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 3, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Bug_1_POC.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