libming up to 0.4.8 util/listmp3.c printMP3Headers memory corruption
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.1 | $0-$5k | 0.00 |
A vulnerability classified as critical has been found in libming up to 0.4.8 (Programming Tool Software). This affects the function printMP3Headers
of the file util/listmp3.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:
The printMP3Headers function in util/listmp3.c in libming v0.4.8 or earlier is vulnerable to a global buffer overflow, which may allow attackers to cause a denial of service via a crafted file, a different vulnerability than CVE-2016-9264.
The bug was discovered 11/21/2017. The weakness was published 11/20/2017 (GitHub Repository). It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2017-16898 since 11/20/2017. 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 of the vulnerability are known, but there is no available exploit.
The vulnerability scanner Nessus provides a plugin with the ID 105753 (Debian DLA-1240-1 : ming security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 277251 (Fedora Security Update for ming (FEDORA-2018-38a0e1e6f5)).
Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (105753).
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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 |
Nessus ID: 105753
Nessus Name: Debian DLA-1240-1 : ming security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 54463
OpenVAS Name: Debian Lts Announce DLA 1240-1 ([SECURITY] [DLA 1240-1] ming security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
11/20/2017 🔍11/20/2017 🔍
11/20/2017 🔍
11/21/2017 🔍
11/21/2017 🔍
01/11/2018 🔍
01/12/2018 🔍
01/11/2023 🔍
Sources
Advisory: 75Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-16898 (🔍)
Entry
Created: 11/21/2017 07:49Updated: 01/11/2023 08:17
Changes: 11/21/2017 07:49 (72), 12/09/2019 08:49 (4), 01/11/2023 08:16 (4), 01/11/2023 08:17 (1)
Complete: 🔍
Cache ID: 3:55B:103
No comments yet. Languages: en.
Please log in to comment.