Application crash via unchecked allocation failure
Published Sep 2, 2025 · Updated Sep 2, 2025
NULL pointer dereference in rust-ffmpeg 0.3.0 allows remote attackers to crash applications that use its input interface. The input() constructor stores a NULL result from avio_alloc_context() in Io, whose Drop implementation later dereferences that pointer. Affected code follows commit 5ac0527; exploitation also requires the allocation to fail, such as under memory exhaustion.
Summary
What happened
NULL pointer dereference in rust-ffmpeg 0.3.0 allows remote attackers to crash applications that use its input interface. The input() constructor stores a NULL result from avio_alloc_context() in Io, whose Drop implementation later dereferences that pointer. Affected code follows commit 5ac0527; exploitation also requires the allocation to fail, such as under memory exhaustion.
The record
- CVE
- CVE-2025-57613
- Published
- Sep 2, 2025
- Updated
- Sep 2, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2025CVE publishedPublication date reported by the CVE source.
- Sep 2, 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
- GitHub issue 192 input allocation-failure triggerproof of concept · unverified
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