squashfs vulnerabilities and fixes
Recent CVEs affecting squashfs, with upgrade or downgrade steps. 4 tracked.
squashfs has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2017-04-13. Highest priority: CVE-2015-4646 (score 55/100).
- CVE-2015-4646 HIGH 7.5 UPGRADE (1) unsquash-1.c, (2) unsquash-2.c, (3) unsquash-3.c, and (4) unsquash-4.c in Squashfs and sasquatch allow rem
- CVE-2015-4645 MEDIUM 5.5 UPGRADE MITIGATE Integer overflow in the read_fragment_table_4 function in unsquash-4.c in Squashfs and sasquatch allows remote
- CVE-2012-4025 MEDIUM 6.8 UPGRADE Integer overflow in the queue_init function in unsquashfs.c in unsquashfs in Squashfs 4.2 and earlier allows r
- CVE-2012-4024 MEDIUM 6.8 UPGRADE Stack-based buffer overflow in the get_component function in unsquashfs.c in unsquashfs in Squashfs 4.2 and ea
FAQ
How do I fix squashfs 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 squashfs being exploited right now?
None of the tracked squashfs CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which squashfs CVE should I patch first?
CVE-2015-4646 currently ranks highest (55/100): (1) unsquash-1.c, (2) unsquash-2.c, (3) unsquash-3.c, and (4) unsquash-4.c in Squashfs and sasquatch allow rem.