CVE-2018-10536: High severity WavPack Wavpack vulnerability
Published Apr 29, 2018
·Updated
An issue was discovered in WavPack 5.1.0 and earlier. The WAV parser component contains a vulnerability that allows writing to memory because ParseRiffHeaderConfig in riff.c does not reject multiple format chunks.
Affected Software
4 affected componentsFixes available
WavPack Wavpack<=5.1.0
Debian Debian Linux=8.0
Debian Debian Linux=9.0
debian/wavpack
5.4.0-15.6.0-15.8.1-15.9.0-1
Remediation
Event History
Apr 29, 2018
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
Data Sourced
via NVD·03:29 PM
RemedyDescriptionSeverityWeaknessAffected Software
Feb 20, 2026
Data Sourced
via Ubuntu·03:53 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·03:54 PM
DescriptionAffected Software
Data Sourced
via Launchpad·03:54 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2018-10536?
CVE-2018-10536 is categorized as a vulnerability that allows writing to memory, which could lead to potential exploitation.
2
How do I fix CVE-2018-10536?
To mitigate CVE-2018-10536, upgrade to WavPack version 5.4.0 or later.
3
Which versions of WavPack are affected by CVE-2018-10536?
WavPack versions 5.1.0 and earlier are affected by CVE-2018-10536.
4
Is CVE-2018-10536 present in Debian Linux?
Yes, CVE-2018-10536 affects Debian Linux versions 8.0 and 9.0 with WavPack installed.
5
What impact does CVE-2018-10536 have on applications?
CVE-2018-10536 may allow an attacker to execute arbitrary code by exploiting the WAV parser vulnerability.