Security readout for executives and security teams
Plain-English summary
CVE-2020-29367 is a heap-based buffer overflow in Blosc C-Blosc2 through 2.0.0.beta.5. It occurs when compressed data is written without enough available space. Business risk depends on whether your software embeds this library and processes compressed data, especially from untrusted sources.
Executive priority
Treat as an inventory-driven memory-safety risk. Prioritize systems that parse compressed data from outside the organization. Urgency is unclear because severity, fixed-version metadata, and exploitation evidence are incomplete.
Technical view
The CVE describes a heap overflow in blosc2.c in C-Blosc2 through 2.0.0.beta.5. Public metadata provides no CVSS score, CWE list, detailed affected CPEs, or confirmed fixed release. References point to an upstream commit and an OSS-Fuzz issue.
Likely exposure
Exposure is most likely in applications, services, or data-processing tools that include C-Blosc2 through 2.0.0.beta.5. The official affected-product metadata is incomplete, so inventory and SBOM verification matter more than product-name matching.
Exploitation context
The source bundle shows an OSS-Fuzz reference, suggesting discovery through fuzz testing. It is not listed in KEV, and the provided sources do not show active exploitation, public exploit use, or exploitation prevalence.
Researcher notes
Key gaps are missing CVSS, CPEs, CWE mapping, and explicit fixed-version guidance in the supplied metadata. The GitHub commit and OSS-Fuzz issue are the primary leads for root-cause and patch confirmation, but no exploit status is supported here.
Mitigation direction
- Inventory direct and transitive use of Blosc C-Blosc2.
- Check vendor guidance, release notes, and the referenced upstream commit.
- Move away from versions through 2.0.0.beta.5 if vendor guidance confirms a fixed build.
- Limit processing of untrusted compressed data until exposure is resolved.
- Monitor the CVE and upstream project for clarified affected and fixed versions.
Validation and detection
- Search SBOMs and dependency manifests for C-Blosc2.
- Confirm deployed versions are not through 2.0.0.beta.5.
- Identify services that process compressed data using this library.
- Review whether compressed inputs can come from untrusted users or partners.
- Run vendor-recommended regression tests after any library update.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2020-29367 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043eeCVE reference · x_refsource_MISC
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.