# OSV-2020-2183: Heap-buffer-overflow in Lizard_decompress_safe

> A heap-buffer-overflow in Lizard_decompress_safe allows attackers to cause denial of service or potentially execute code via crafted compressed data.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2020

## What is OSV-2020-2183?

OSV-2020-2183 is a memory corruption vulnerability in c-blosc2, published on 25 Nov 2020. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27818

```
Crash type: Heap-buffer-overflow READ 2
Crash state:
Lizard_decompress_safe
blosc_d
do_job
```

## Which versions are affected by OSV-2020-2183?

1 open source package ship an affected version, including c-blosc2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `c-blosc2` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2020-2183?

No fix has been published for OSV-2020-2183 yet. Limit exposure of the affected software until one is available.

## Is OSV-2020-2183 being exploited?

There is no known exploitation of OSV-2020-2183 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-2183 and fix it if it is affected.

What it is: OSV-2020-2183 is a memory corruption vulnerability in c-blosc2, published on 25 Nov 2020. 
Exploitation: There is no known exploitation of OSV-2020-2183 in the wild and no public exploit code.

Affected packages and fixed versions:
- c-blosc2 (OSS-Fuzz): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/OSV-2020-2183/ (Markdown: https://insights.sbomify.com/OSV-2020-2183/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-2183

---
From sbomify Insights: https://insights.sbomify.com/OSV-2020-2183/
Summaries are generated and may contain mistakes; the official description above is the record.