c-blosc2 vulnerabilities and fixes
Recent CVEs affecting c-blosc2, with upgrade or downgrade steps. 6 tracked.
Also searched as: c blosc2.
c-blosc2 has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2024-04-02. Highest priority: CVE-2024-3204 (score 53/100).
- CVE-2024-3204 HIGH 7.3 UPGRADE A vulnerability has been found in c-blosc2 up to 2.13.2 and classified as critical
- CVE-2024-3203 HIGH 7.3 UPGRADE A vulnerability, which was classified as critical, was found in c-blosc2 up to 2.13.2
- CVE-2023-37188 HIGH 7.5 UPGRADE C-blosc2 before 2.9.3 was discovered to contain a NULL pointer dereference via the function zfp_rate_decompres
- CVE-2023-37187 HIGH 7.5 UPGRADE C-blosc2 before 2.9.3 was discovered to contain a NULL pointer dereference via the zfp/blosc2-zfp.c zfp_acc_de
- CVE-2023-37186 HIGH 7.5 UPGRADE C-blosc2 before 2.9.3 was discovered to contain a NULL pointer dereference in ndlz/ndlz8x8.c via a NULL pointe
- CVE-2023-37185 HIGH 7.5 UPGRADE C-blosc2 before 2.9.3 was discovered to contain a NULL pointer dereference via the function zfp_prec_decompres
FAQ
How do I fix c-blosc2 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 c-blosc2 being exploited right now?
None of the tracked c-blosc2 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which c-blosc2 CVE should I patch first?
CVE-2024-3204 currently ranks highest (53/100): A vulnerability has been found in c-blosc2 up to 2.13.2 and classified as critical.