Information disclosure via unreleased SampleArray allocation
Published Feb 19, 2025 · Updated Feb 20, 2025
Memory leak in Bento4 1.6.0-641 allows attackers to read sensitive information by supplying a malformed MP4 file to mp4fragment. When sample-cursor initialization fails, mp4fragment skips the track after allocating a SampleArray and leaves that object and related allocations unreleased. Exploitation requires crafted content to be processed; the public demonstration reports 737 leaked bytes under LeakSanitizer but does not demonstrate retrieval of the leaked data.
Summary
What happened
Memory leak in Bento4 1.6.0-641 allows attackers to read sensitive information by supplying a malformed MP4 file to mp4fragment. When sample-cursor initialization fails, mp4fragment skips the track after allocating a SampleArray and leaves that object and related allocations unreleased. Exploitation requires crafted content to be processed; the public demonstration reports 737 leaked bytes under LeakSanitizer but does not demonstrate retrieval of the leaked data.
The record
- CVE
- CVE-2025-25942
- Published
- Feb 19, 2025
- Updated
- Feb 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-200, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 19, 2025CVE publishedPublication date reported by the CVE source.
- Feb 20, 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?
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.
Weakness, pattern, technique
Public exploit references
- bug5.mp4 proof-of-concept fileproof 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