Skip to content
Fencer Intel
high 7.8

CVE-2020-29367 json

blosc2 heap-based buffer overflow

published 5y ago modified last mo. also GHSA-8c7c-2c8j-3xfp , PYSEC-2020-343 , EUVD-2020-0243

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits
0
none known

Summary

blosc2.c in Blosc C-Blosc2 through 2.0.0.beta.5 has a heap-based buffer overflow when there is a lack of space to write compressed data.

Patch / fix

  • pypi blosc2 0.1.7
  • blosc Package Hub 15 SP2, Package Hub 15 SP1, openSUSE Leap 15.2 +1 more 1.20.1-bp152.4.3.1

opensuse advisories openSUSE-SU-2020:2337-1

Is CVE-2020-29367 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-29367 updated cvss 7.4

blosc: heap-based buffer overflow when there is a lack of space to write compressed data

  • Red Hat OpenShift Container Platform 4 blosc, blosc-bench Red Hat OpenStack Platform 13 (Queens) blosc Red Hat OpenStack Platform 16.1 blosc
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
GitHub 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi blosc2
<0.1.7
0.1.7

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.