Simple DirectMedia Layer up to 1.2.15/2.0.9 audio/SDL_wave.c IMA_ADPCM_nibble memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Simple DirectMedia Layer up to 1.2.15/2.0.9. It has been classified as critical. The affected element is the function IMA_ADPCM_nibble of the file audio/SDL_wave.c. Performing a manipulation results in memory corruption.
This vulnerability was named CVE-2019-7572. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as critical has been found in Simple DirectMedia Layer up to 1.2.15/2.0.9. This affects the function IMA_ADPCM_nibble of the file audio/SDL_wave.c. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
SDL (Simple DirectMedia Layer) through 1.2.15 and 2.x through 2.0.9 has a buffer over-read in IMA_ADPCM_nibble in audio/SDL_wave.c.
The bug was discovered 02/07/2019. The weakness was presented 02/07/2019 (Website). The advisory is shared at lists.fedoraproject.org. This vulnerability is uniquely identified as CVE-2019-7572 since 02/07/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The commercial vulnerability scanner Qualys is able to test this issue with plugin 277627 (Fedora Security Update for SDL (FEDORA-2019-7a554204c1)).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-130654, VDB-130655, VDB-130656 and VDB-130657 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 1.2.0
- 1.2.1
- 1.2.2
- 1.2.3
- 1.2.4
- 1.2.5
- 1.2.6
- 1.2.7
- 1.2.8
- 1.2.9
- 1.2.10
- 1.2.11
- 1.2.12
- 1.2.13
- 1.2.14
- 1.2.15
- 2.0.0
- 2.0.1
- 2.0.2
- 2.0.3
- 2.0.4
- 2.0.5
- 2.0.6
- 2.0.7
- 2.0.8
- 2.0.9
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.6
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
02/07/2019 🔍02/07/2019 🔍
02/07/2019 🔍
02/08/2019 🔍
07/06/2023 🔍
Sources
Advisory: USN-4156-1Status: Confirmed
CVE: CVE-2019-7572 (🔍)
GCVE (CVE): GCVE-0-2019-7572
GCVE (VulDB): GCVE-100-130653
See also: 🔍
Entry
Created: 02/08/2019 09:44Updated: 07/06/2023 21:00
Changes: 02/08/2019 09:44 (56), 05/09/2020 09:41 (2), 07/06/2023 21:00 (3)
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.