OSV-2020-105 Segv on unknown address in cbor_typeof
Not scored
Published
Check this codebase for OSV-2020-105 and fix it if it is affected.
What it is: OSV-2020-105 is a vulnerability in libcbor, published on 24 Jun 2020.
Exploitation: There is no known exploitation of OSV-2020-105 in the wild and no public exploit code.
Affected packages and fixed versions:
- libcbor (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-105/ (Markdown: https://insights.sbomify.com/OSV-2020-105/index.md)
A null pointer dereference in the CBOR parsing library allows attackers to cause a denial of service via crafted input.
- 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-105?
OSV-2020-105 is a vulnerability in libcbor, published on 24 Jun 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=21387
Crash type: Segv on unknown address
Crash state:
cbor_typeof
_cbor_nested_describe
_cbor_nested_describe
Which versions are affected by OSV-2020-105?
1 open source package ship an affected version, including libcbor.
| Package | Affected | Fixed in |
|---|---|---|
libcbor OSS-Fuzz | All versions | None |
How do I fix OSV-2020-105?
No fix has been published for OSV-2020-105 yet. Limit exposure of the affected software until one is available.
Is OSV-2020-105 being exploited?
There is no known exploitation of OSV-2020-105 in the wild and no public exploit code.