VDB-117202 · CVE-2018-10540 · Qualys 197125

Wavpack up to 5.1.0 W64 Parser wave64.c ParseWave64HeaderConfig out-of-bounds write

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.

A vulnerability has been found in Wavpack up to 5.1.0 and classified as critical. This vulnerability affects the function ParseWave64HeaderConfig of the file wave64.c of the component W64 Parser. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-787. As an impact it is known to affect confidentiality, integrity, and availability.

The bug was discovered 04/23/2018. The weakness was disclosed 04/29/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-10540 since 04/29/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 109469 (Ubuntu 17.10 / 18.04 LTS : wavpack vulnerabilities (USN-3637-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Ubuntu Local Security Checks and running in the context local. The commercial vulnerability scanner Qualys is able to test this issue with plugin 197125 (Ubuntu Security Notification for Wavpack Vulnerabilities (USN-3637-1)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 1 days after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (109469). The entries 117198, 117199, 117200 and 117201 are pretty similar.



CPE 2.3infoedit

CPE 2.2infoedit


VulDB Meta Base Score: 5.4
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.5
NVD Vector: 🔍



VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍


Class: Memory corruption
CWE: CWE-787
ATT&CK: Unknown

Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍


Nessus ID: 109469
Nessus Name: Ubuntu 17.10 / 18.04 LTS : wavpack vulnerabilities (USN-3637-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 53695
OpenVAS Name: Fedora Update for wavpack FEDORA-2018-d6002f761d
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfoedit

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍


Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: github.com


04/23/2018 🔍
04/29/2018 +5 days 🔍
04/29/2018 +0 days 🔍
04/29/2018 +0 days 🔍
04/30/2018 +1 days 🔍
04/30/2018 +0 days 🔍
05/01/2018 +1 days 🔍
02/01/2020 +641 days 🔍


Advisory: github.com
Status: Not defined

CVE: CVE-2018-10540 (🔍)
See also: 🔍


Created: 04/30/2018 09:06 AM
Updated: 02/01/2020 10:47 AM
Changes: (3) vulnerability_discoverydate countermeasure_name countermeasure_date
Complete: 🔍


No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!