OSV-2017-62 Use-of-uninitialized-value in gnutls_memset
Not scored
Published
Check this codebase for OSV-2017-62 and fix it if it is affected.
What it is: OSV-2017-62 is a vulnerability in gnutls, published on 13 Jan 2021. 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-2017-62 in the wild and no public exploit code.
Affected packages and fixed versions:
- gnutls (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-2017-62/ (Markdown: https://insights.sbomify.com/OSV-2017-62/index.md)
An attacker can potentially read uninitialized memory during TLS handshake cleanup, 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-2017-62?
OSV-2017-62 is a vulnerability in gnutls, published on 13 Jan 2021. 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=1493
Crash type: Use-of-uninitialized-value
Crash state:
gnutls_memset
deinit_keys
_gnutls_handshake_internal_state_clear
Which versions are affected by OSV-2017-62?
1 open source package ship an affected version, including gnutls.
| Package | Affected | Fixed in |
|---|---|---|
gnutls OSS-Fuzz | All versions | None |
How do I fix OSV-2017-62?
No fix has been published for OSV-2017-62 yet. Limit exposure of the affected software until one is available.
Is OSV-2017-62 being exploited?
There is no known exploitation of OSV-2017-62 in the wild and no public exploit code.