OSV-2020-630 Use-of-uninitialized-value in ares__parse_into_addrinfo2
Not scored
Published
Check this codebase for OSV-2020-630 and fix it if it is affected.
What it is: OSV-2020-630 is a vulnerability in c-ares, published on 1 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of OSV-2020-630 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-630/ (Markdown: https://insights.sbomify.com/OSV-2020-630/index.md)
An attacker can trigger a use-of-uninitialized-value bug in the c-ares DNS library, potentially leading to information disclosure.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2020-630?
OSV-2020-630 is a vulnerability in c-ares, published on 1 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15379
Crash type: Use-of-uninitialized-value
Crash state:
ares__parse_into_addrinfo2
ares_parse_aaaa_reply
ares-test-fuzz.c
Which versions are affected by OSV-2020-630?
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-630?
No fix has been published for OSV-2020-630 yet. Limit exposure of the affected software until one is available.
Is OSV-2020-630 being exploited?
There is no known exploitation of OSV-2020-630 in the wild and no public exploit code.