OSV-2020-1060 Use-of-uninitialized-value in ZSTD_createDDict_advanced
Not scored
Published
Check this codebase for OSV-2020-1060 and fix it if it is affected.
What it is: OSV-2020-1060 is a vulnerability in c-blosc2, published on 22 Jul 2020.
Exploitation: There is no known exploitation of OSV-2020-1060 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-1060/ (Markdown: https://insights.sbomify.com/OSV-2020-1060/index.md)
A use-of-uninitialized-value bug in the Zstandard library can cause a crash during dictionary creation, potentially leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2020-1060?
OSV-2020-1060 is a vulnerability in c-blosc2, published on 22 Jul 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=23732
Crash type: Use-of-uninitialized-value
Crash state:
ZSTD_createDDict_advanced
ZSTD_createDDict
blosc_run_decompression_with_context
Which versions are affected by OSV-2020-1060?
1 open source package ship an affected version, including c-blosc2.
| Package | Affected | Fixed in |
|---|---|---|
c-blosc2 OSS-Fuzz | All versions | None |
How do I fix OSV-2020-1060?
No fix has been published for OSV-2020-1060 yet. Limit exposure of the affected software until one is available.
Is OSV-2020-1060 being exploited?
There is no known exploitation of OSV-2020-1060 in the wild and no public exploit code.