cabextract project vulnerabilities
Recent CVEs affecting cabextract project products. 6 tracked.
cabextract project has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2019-11-29. Highest priority: CVE-2018-14682 (score 58/100).
- CVE-2018-18584 MEDIUM 6.5 UPGRADE DOWNGRADE In mspack/cab.h in libmspack before 0.8alpha and cabextract before 1.8, the CAB block input buffer is one byte
- CVE-2018-14682 HIGH 8.8 DOWNGRADE UPGRADE An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha
- CVE-2018-14681 HIGH 8.8 DOWNGRADE UPGRADE An issue was discovered in kwajd_read_headers in mspack/kwajd.c in libmspack before 0.7alpha
- CVE-2018-14680 MEDIUM 6.5 DOWNGRADE UPGRADE An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha
- CVE-2018-14679 MEDIUM 6.5 DOWNGRADE UPGRADE An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha
- CVE-2015-2060 MEDIUM 5.3 UPGRADE cabextract before 1.6 does not properly check for leading slashes when extracting files, which allows remote a
FAQ
How do I fix cabextract 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 cabextract project being exploited right now?
None of the tracked cabextract project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which cabextract project CVE should I patch first?
CVE-2018-14682 currently ranks highest (58/100): An issue was discovered in mspack/chmd.c in libmspack before 0.7alpha.