blosc: heap-based buffer overflow when there is a lack of space to write compressed data
Published Nov 27, 2020
7.8
HIGHCVSS 3.1
EPSS 1.20%
Description
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.
Affected products
No data.
- 2.0.0
- 2.0.0
- 2.0.0
- 2.0.0
- 2.0.0
- 2.0.0
- 2.0.0
- 2.0.0
- 2.0.0
No data.
Red Hat OpenShift Container Platform 4
blosc
Will not fix
Red Hat OpenStack Platform 13 (Queens)
blosc
Will not fix
Red Hat OpenStack Platform 16.1
blosc
Will not fix
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4 | blosc | Will not fix | n/a |
| Red Hat OpenStack Platform 13 (Queens) | blosc | Will not fix | n/a |
| Red Hat OpenStack Platform 16.1 | blosc | Will not fix | n/a |
No package ranges for this CVE.
Remediation
Red Hat statement
OpenShift Container Platform (OCP) 4 temporarily shipped one version of the blosc package in OCP 4.3.0. Updates to the blosc package, which is used in the ironic-hardware-inventory-recorder-image container are consumed from OpenStack Platform 16 repositories. In Red Hat OpenStack Platform, because the flaw has a lower impact and the fix would require a substantial amount of development, no update will be provided at this time for the RHOSP blosc package.
Metrics
No CVSS v4.0 score for this CVE.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
1 other source (Red Hat) ▾
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
No CVSS v3.0 score for this CVE.
AV:N/AC:M/Au:N/C:C/I:C/A:C
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Table of values (11 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 1.20% (0.01201) | 67.09th | v5 (v2026.06.15) |
| Sep 20, 2026 | 1.20% (0.01201) | 66.82th | v5 (v2026.06.15) |
| Jul 20, 2024 | 0.09% (0.00086) | 37.13th | v3 (v2023.03.01) |
| Sep 3, 2023 | 0.09% (0.00086) | 35.59th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.07% (0.00068) | 27.62th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.89% (0.00885) | 27.89th | v2 (v2022.01.01) |
| Feb 4, 2022 | 1.40% (0.01404) | 49.02th | v2 (v2022.01.01) |
| Feb 3, 2022 | 2.74% (0.02742) | 63.06th | v1 |
| Jan 6, 2022 | 2.74% (0.02742) | 62.72th | v1 |
| Jan 5, 2022 | 0.62% (0.00624) | 46.35th | v5 (v2026.06.15) |
| Apr 14, 2021 | 0.62% (0.00624) | 0.00th | v1 |
References (9)
- https://access.redhat.com/security/cve/CVE-2020-29367 Vendor Advisory
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442 x_refsource_MISCMailing ListThird Party Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=1903232 Issue Tracking
- https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043ee x_refsource_MISCPatchThird Party Advisory
- https://github.com/Blosc/python-blosc2/releases/tag/v0.1.7
- https://github.com/advisories/GHSA-8c7c-2c8j-3xfp Advisory
- https://github.com/pypa/advisory-database/tree/main/vulns/blosc2/PYSEC-2020-343.yaml
- https://nvd.nist.gov/vuln/detail/CVE-2020-29367
- https://www.cve.org/CVERecord?id=CVE-2020-29367
| Link | Providers | Tags |
|---|---|---|
| https://access.redhat.com/security/cve/CVE-2020-29367 | Vendor Advisory | |
| https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442 | x_refsource_MISCMailing ListThird Party Advisory | |
| https://bugzilla.redhat.com/show_bug.cgi?id=1903232 | Issue Tracking | |
| https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043ee | x_refsource_MISCPatchThird Party Advisory | |
| https://github.com/Blosc/python-blosc2/releases/tag/v0.1.7 | ||
| https://github.com/advisories/GHSA-8c7c-2c8j-3xfp | Advisory | |
| https://github.com/pypa/advisory-database/tree/main/vulns/blosc2/PYSEC-2020-343.yaml | ||
| https://nvd.nist.gov/vuln/detail/CVE-2020-29367 | ||
| https://www.cve.org/CVERecord?id=CVE-2020-29367 |
Change history (0)
No recorded changes yet.