Libsndfile 1.2.2 IRCAM Audio File src/ircam.c ircam_read_header memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Libsndfile 1.2.2. This affects the function ircam_read_header of the file src/ircam.c of the component IRCAM Audio File Handler. The manipulation leads to memory corruption.
This vulnerability is listed as CVE-2025-52194. There is no available exploit.
Details
A vulnerability, which was classified as critical, has been found in Libsndfile 1.2.2. This issue affects the function ircam_read_header of the file src/ircam.c of the component IRCAM Audio File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A buffer overflow vulnerability exists in libsndfile version 1.2.2 and potentially earlier versions when processing malformed IRCAM audio files. The vulnerability occurs in the ircam_read_header function at src/ircam.c:164 during sample rate processing, leading to memory corruption and potential code execution.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-52194 since 06/16/2025. The exploitation is known to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/11/2025).
The vulnerability scanner Nessus provides a plugin with the ID 260191 (Linux Distros Unpatched Vulnerability : CVE-2025-52194), which helps to determine the existence of the flaw in a target environment.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at Tenable (260191) and CERT Bund (WID-SEC-2025-1890). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Open Source libsndfile
Product
Type
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 260191
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-52194
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/16/2025 CVE reserved08/21/2025 Advisory disclosed
08/21/2025 VulDB entry created
09/11/2025 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2025-52194 (🔒)
GCVE (CVE): GCVE-0-2025-52194
GCVE (VulDB): GCVE-100-320933
CERT Bund: WID-SEC-2025-1890 - libsndfile: Schwachstelle ermöglicht Codeausführung und DoS
Entry
Created: 08/21/2025 16:39Updated: 09/11/2025 21:14
Changes: 08/21/2025 16:39 (55), 08/25/2025 06:13 (7), 09/02/2025 01:38 (2), 09/11/2025 21:14 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.