Denial of service via unreleased memory
Published Sep 30, 2022 · Updated May 20, 2025
A memory leak in Bento4 1.6.0-639 allows local users to cause a denial of service by processing a crafted media file. The AP4_StdcFileByteStream::Create function fails to release allocated memory during file-byte-stream creation, allowing repeated processing to exhaust available memory. Exploitation requires local access and user interaction with a crafted file; the bounded impact is service interruption without confidentiality or integrity loss.
Summary
What happened
A memory leak in Bento4 1.6.0-639 allows local users to cause a denial of service by processing a crafted media file. The AP4_StdcFileByteStream::Create function fails to release allocated memory during file-byte-stream creation, allowing repeated processing to exhaust available memory. Exploitation requires local access and user interaction with a crafted file; the bounded impact is service interruption without confidentiality or integrity loss.
The record
- CVE
- CVE-2022-41847
- Published
- Sep 30, 2022
- Updated
- May 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-401, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 30, 2022CVE publishedPublication date reported by the CVE source.
- May 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
No public exploit references are available in this record.
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