PatchTheCVEhalibut vulnerabilities and fixes
Recent CVEs affecting halibut, with upgrade or downgrade steps. 4 tracked.
halibut has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2022-05-24. Highest priority: CVE-2021-31819 (score 60/100).
- CVE-2021-42614 HIGH 7.8 DOWNGRADE MITIGATE A use after free in info_width_internal in bk_info.c in Halibut 1.2 allows an attacker to cause a segmentation
- CVE-2021-42613 HIGH 7.8 DOWNGRADE MITIGATE A double free in cleanup_index in index.c in Halibut 1.2 allows an attacker to cause a denial of service or po
- CVE-2021-42612 HIGH 7.8 DOWNGRADE MITIGATE A use after free in cleanup_index in index.c in Halibut 1.2 allows an attacker to cause a segmentation fault o
- CVE-2021-31819 CRITICAL 9.8 UPGRADE In Halibut versions prior to 4.4.7 there is a deserialisation vulnerability that could allow remote code execu
FAQ
How do I fix halibut 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 halibut being exploited right now?
None of the tracked halibut CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which halibut CVE should I patch first?
CVE-2021-31819 currently ranks highest (60/100): In Halibut versions prior to 4.4.7 there is a deserialisation vulnerability that could allow remote code execu.