Application crash via null FileModule dereference
Published Oct 23, 2025 · Updated Oct 23, 2025
NULL pointer dereference in Audiofile 0.3.7 allows attackers to crash an application that processes a crafted audio file. ModuleState::setup accesses a null FileModule pointer when sfconvert calls afGetFrameCount while processing the malformed input. Processing the file is required, and the demonstrated consequence is a read from address zero followed by a segmentation fault.
Summary
What happened
NULL pointer dereference in Audiofile 0.3.7 allows attackers to crash an application that processes a crafted audio file. ModuleState::setup accesses a null FileModule pointer when sfconvert calls afGetFrameCount while processing the malformed input. Processing the file is required, and the demonstrated consequence is a read from address zero followed by a segmentation fault.
The record
- CVE
- CVE-2025-50950
- Published
- Oct 23, 2025
- Updated
- Oct 23, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 23, 2025CVE publishedPublication date reported by the CVE source.
- Oct 23, 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.
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
- Issue #66 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