CVE-2025-50950
BaseFortify
Publication date: 2025-10-23
Last updated on: 2025-10-28
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| audiofile | audiofile | 0.3.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-50950 is a null pointer dereference vulnerability in the audiofile project, specifically in the function ModuleState::setup. The function attempts to access a member of a FileModule struct through a null pointer, causing the application to crash with a segmentation fault when processing certain malformed audio files. [1]
How can this vulnerability impact me? :
This vulnerability can cause a denial of service by crashing the application when it processes specially crafted malformed audio files, potentially disrupting service or functionality relying on the audiofile library. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by running the vulnerable `sfconvert` utility with a specially crafted proof-of-concept (poc) audio file that triggers the null pointer dereference and causes a crash. Detection involves monitoring for segmentation faults (SEGV) in `sfconvert` during processing. Additionally, compiling the audiofile project with AddressSanitizer enabled using flags `-g -O0 -fsanitize=address,undefined` and running tests can help identify the issue. Example commands include compiling with `afl-gcc` or `afl-g++` using these flags and executing `./sfconvert poc_file` to observe crashes. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include avoiding the use of the vulnerable `sfconvert` utility on untrusted or malformed audio files to prevent crashes. Since no patches or fixes are provided, restricting access to the utility and monitoring for crashes can reduce impact. Consider running the utility in a controlled environment or sandbox to limit denial of service effects. Await official patches or updates from the audiofile project for a permanent fix. [1]