OSV-2024-1293 Use-of-uninitialized-value in k5_hashtab_add
Not scored
Published
Check this codebase for OSV-2024-1293 and fix it if it is affected.
What it is: OSV-2024-1293 is a vulnerability in krb5, published on 8 Nov 2024.
Exploitation: There is no known exploitation of OSV-2024-1293 in the wild and no public exploit code.
Affected packages and fixed versions:
- krb5 (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-2024-1293/ (Markdown: https://insights.sbomify.com/OSV-2024-1293/index.md)
An uninitialized value in the Kerberos hash table addition function can cause a crash, potentially leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2024-1293?
OSV-2024-1293 is a vulnerability in krb5, published on 8 Nov 2024.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=377530685
Crash type: Use-of-uninitialized-value
Crash state:
k5_hashtab_add
insert_entry
fuzz_kdc.c
Which versions are affected by OSV-2024-1293?
1 open source package ship an affected version, including krb5.
| Package | Affected | Fixed in |
|---|---|---|
krb5 OSS-Fuzz | All versions | None |
How do I fix OSV-2024-1293?
No fix has been published for OSV-2024-1293 yet. Limit exposure of the affected software until one is available.
Is OSV-2024-1293 being exploited?
There is no known exploitation of OSV-2024-1293 in the wild and no public exploit code.