wavpack vulnerabilities and fixes
Recent CVEs affecting wavpack, with upgrade or downgrade steps. 3 tracked.
wavpack has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2022-07-19. Highest priority: CVE-2020-35738 (score 48/100).
- CVE-2022-2476 MEDIUM 5.5 DOWNGRADE MITIGATE A null pointer dereference bug was found in wavpack-5.4.0 The results from the ASAN log: AddressSanitizer:DEAD
- CVE-2021-44269 MEDIUM 5.5 DOWNGRADE MITIGATE An out of bounds read was found in Wavpack 5.4.0 in processing *.WAV files
- CVE-2020-35738 MEDIUM 6.1 DOWNGRADE MITIGATE WavPack 5.3.0 has an out-of-bounds write in WavpackPackSamples in pack_utils.c because of an integer overflow
FAQ
How do I fix wavpack vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is wavpack being exploited right now?
None of the tracked wavpack CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which wavpack CVE should I patch first?
CVE-2020-35738 currently ranks highest (48/100): WavPack 5.3.0 has an out-of-bounds write in WavpackPackSamples in pack_utils.c because of an integer overflow .