Process crash via oversized memory-stream copy
Published Sep 14, 2022 · Updated Aug 3, 2024
Buffer overflow in Bento4 1.6.0-639 allows remote attackers to crash mp42aac by supplying a crafted ISO-MP4 media file. For the published input, AP4_MemoryByteStream::WritePartial passes a 4,294,967,288-byte length to memcpy after allocating a 1,056-byte destination buffer. The attack requires mp42aac to process the file; the demonstrated consequence is a process crash with no reported data disclosure or modification.
Summary
What happened
Buffer overflow in Bento4 1.6.0-639 allows remote attackers to crash mp42aac by supplying a crafted ISO-MP4 media file. For the published input, AP4_MemoryByteStream::WritePartial passes a 4,294,967,288-byte length to memcpy after allocating a 1,056-byte destination buffer. The attack requires mp42aac to process the file; the demonstrated consequence is a process crash with no reported data disclosure or modification.
The record
- CVE
- CVE-2022-40438
- Published
- Sep 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 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.
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
- Bento4 issue 751 crash inputproof 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