Decoder crash via invalid MP4 metadata access
Published Aug 15, 2023 · Updated Aug 2, 2024
Invalid memory access in FAAD2 2.10.1 allows remote attackers to crash the faad command-line decoder via a crafted MP4 file. The mp4info function reads from the near-null address 0x4 at mp4read.c line 1039 while extracting metadata from malformed input. Exploitation requires user interaction to make faad process the file; the published ASAN trace demonstrates process termination, not code execution.
Summary
What happened
Invalid memory access in FAAD2 2.10.1 allows remote attackers to crash the faad command-line decoder via a crafted MP4 file. The mp4info function reads from the near-null address 0x4 at mp4read.c line 1039 while extracting metadata from malformed input. Exploitation requires user interaction to make faad process the file; the published ASAN trace demonstrates process termination, not code execution.
The record
- CVE
- CVE-2023-38858
- Published
- Aug 15, 2023
- Updated
- Aug 2, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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
- faad2 segv 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