OSV-2018-122 Use-of-uninitialized-value in gnutls_pkcs12_get_bag
Not scored
Published
Check this codebase for OSV-2018-122 and fix it if it is affected.
What it is: OSV-2018-122 is a vulnerability in gnutls, published on 13 Jan 2021.
Exploitation: There is no known exploitation of OSV-2018-122 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-2018-122/ (Markdown: https://insights.sbomify.com/OSV-2018-122/index.md)
An attacker can cause a denial of service in applications using GnuTLS by triggering a use-of-uninitialized-value error during PKCS12 parsing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2018-122?
OSV-2018-122 is a vulnerability in gnutls, published on 13 Jan 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10136
Crash type: Use-of-uninitialized-value
Crash state:
gnutls_pkcs12_get_bag
gnutls_pkcs12_simple_parse
gnutls_pkcs12_key_parser_fuzzer.c
Which versions are affected by OSV-2018-122?
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-2018-122?
No fix has been published for OSV-2018-122 yet. Limit exposure of the affected software until one is available.
Is OSV-2018-122 being exploited?
There is no known exploitation of OSV-2018-122 in the wild and no public exploit code.