PatchTheCVEwavpack project vulnerabilities
Recent CVEs affecting wavpack project products. 4 tracked.
wavpack project has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2017-03-14. Highest priority: CVE-2016-10172 (score 45/100).
- CVE-2016-10172 MEDIUM 5.5 UPGRADE The read_new_config_info function in open_utils.c in Wavpack before 5.1.0 allows remote attackers to cause a d
- CVE-2016-10171 MEDIUM 5.5 UPGRADE The unreorder_channels function in cli/wvunpack.c in Wavpack before 5.1.0 allows remote attackers to cause a d
- CVE-2016-10170 MEDIUM 5.5 UPGRADE The WriteCaffHeader function in cli/caff.c in Wavpack before 5.1.0 allows remote attackers to cause a denial o
- CVE-2016-10169 MEDIUM 5.5 UPGRADE The read_code function in read_words.c in Wavpack before 5.1.0 allows remote attackers to cause a denial of se
FAQ
How do I fix wavpack project 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 project being exploited right now?
None of the tracked wavpack project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which wavpack project CVE should I patch first?
CVE-2016-10172 currently ranks highest (45/100): The read_new_config_info function in open_utils.c in Wavpack before 5.1.0 allows remote attackers to cause a d.