aubio 0.4.6 io/source_avcodec.c aubio_source_avcodec_readframe memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in aubio 0.4.6. It has been rated as critical. Affected by this issue is the function aubio_source_avcodec_readframe
of the file io/source_avcodec.c. The manipulation leads to memory corruption.
This vulnerability is handled as CVE-2018-14521. The attack may be launched remotely. There is no exploit available.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in aubio 0.4.6. It has been declared as critical. Affected by this vulnerability is the function aubio_source_avcodec_readframe
of the file io/source_avcodec.c. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in aubio 0.4.6. A SEGV signal can occur in aubio_source_avcodec_readframe in io/source_avcodec.c, as demonstrated by aubiomfcc.
The bug was discovered 07/22/2018. The weakness was published 07/23/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-14521 since 07/22/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.5VulDB Meta Temp Score: 7.5
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: 🔍
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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/22/2018 🔍07/22/2018 🔍
07/23/2018 🔍
07/23/2018 🔍
07/23/2018 🔍
04/25/2023 🔍
Sources
Advisory: 187Status: Not defined
CVE: CVE-2018-14521 (🔍)
GCVE (CVE): GCVE-0-2018-14521
GCVE (VulDB): GCVE-100-122065
Entry
Created: 07/23/2018 01:58 PMUpdated: 04/25/2023 09:34 AM
Changes: 07/23/2018 01:58 PM (57), 03/09/2020 01:10 PM (1), 04/25/2023 09:34 AM (3)
Complete: 🔍
Cache ID: 18:DBB:40
No comments yet. Languages: en.
Please log in to comment.