What is CVE-2020-29367?

CVE-2020-29367 is a high-severity out-of-bounds write vulnerability in blosc2 (pip), affecting versions < 0.1.7. It is fixed in 0.1.7. A write operation targets a memory location beyond the intended buffer boundary.

How severe is CVE-2020-29367?

CVE-2020-29367 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of blosc2 are affected by CVE-2020-29367?

blosc2 (pip) versions < 0.1.7 is affected.

Is there a fix for CVE-2020-29367?

Yes. CVE-2020-29367 is fixed in 0.1.7. Upgrade to this version or later.

Is CVE-2020-29367 exploitable, and should I be worried?

Whether CVE-2020-29367 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2020-29367 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2020-29367 in blosc2

Q: How severe is CVE-2020-29367?

CVE-2020-29367 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of blosc2 are affected by CVE-2020-29367?

blosc2 (pip) versions < 0.1.7 is affected.

Q: Is there a fix for CVE-2020-29367?

Yes. CVE-2020-29367 is fixed in 0.1.7. Upgrade to this version or later.

Q: Is CVE-2020-29367 exploitable, and should I be worried?

Whether CVE-2020-29367 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2020-29367 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2020-29367?

Upgrade blosc2 to 0.1.7 or later.

Summary

blosc2 heap-based buffer overflow

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.

Impact

A write operation targets a memory location beyond the intended buffer boundary. Typical impact: memory corruption, crash, or arbitrary code execution.

CVE-2020-29367 has a CVSS score of 7.8 (High). The vector is requires local access, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.1.7); upgrading removes the vulnerable code path.

Affected versions

blosc2 (< 0.1.7)

Security releases

blosc2 → 0.1.7 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade blosc2 to 0.1.7 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2020-29367? CVE-2020-29367 is a high-severity out-of-bounds write vulnerability in blosc2 (pip), affecting versions < 0.1.7. It is fixed in 0.1.7. A write operation targets a memory location beyond the intended buffer boundary.
How severe is CVE-2020-29367? CVE-2020-29367 has a CVSS score of 7.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of blosc2 are affected by CVE-2020-29367? blosc2 (pip) versions < 0.1.7 is affected.
Is there a fix for CVE-2020-29367? Yes. CVE-2020-29367 is fixed in 0.1.7. Upgrade to this version or later.
Is CVE-2020-29367 exploitable, and should I be worried? Whether CVE-2020-29367 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2020-29367 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2020-29367? Upgrade blosc2 to 0.1.7 or later.