OSV-2020-280 Null-dereference READ
Not scored
Published
Check this codebase for OSV-2020-280 and fix it if it is affected.
What it is: OSV-2020-280 is a vulnerability in c-ares, published on 30 Jun 2020.
Exploitation: There is no known exploitation of OSV-2020-280 in the wild and no public exploit code.
Affected packages and fixed versions:
- c-ares (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-280/ (Markdown: https://insights.sbomify.com/OSV-2020-280/index.md)
A null pointer dereference in an OSS-Fuzz reported library can cause a crash, leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is OSV-2020-280?
OSV-2020-280 is a vulnerability in c-ares, published on 30 Jun 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15458
Crash type: Null-dereference READ
Crash state:
NULL```
Which versions are affected by OSV-2020-280?
1 open source package ship an affected version, including c-ares.
| Package | Affected | Fixed in |
|---|---|---|
c-ares OSS-Fuzz | All versions | None |
How do I fix OSV-2020-280?
No fix has been published for OSV-2020-280 yet. Limit exposure of the affected software until one is available.
Is OSV-2020-280 being exploited?
There is no known exploitation of OSV-2020-280 in the wild and no public exploit code.