OSV-2024-177 Heap-buffer-overflow in p11_rpc_buffer_get_date_value
Not scored
Published
Check this codebase for OSV-2024-177 and fix it if it is affected.
What it is: OSV-2024-177 is a memory corruption vulnerability in p11-kit, published on 16 Mar 2024.
Exploitation: There is no known exploitation of OSV-2024-177 in the wild and no public exploit code.
Affected packages and fixed versions:
- p11-kit (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-177/ (Markdown: https://insights.sbomify.com/OSV-2024-177/index.md)
A heap buffer overflow in the PKCS#11 RPC library allows attackers to cause crashes or potentially execute arbitrary code via crafted messages.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2024-177?
OSV-2024-177 is a memory corruption vulnerability in p11-kit, published on 16 Mar 2024.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67383
Crash type: Heap-buffer-overflow WRITE 8
Crash state:
p11_rpc_buffer_get_date_value
p11_rpc_message_get_date_value
p11_rpc_message_get_attribute
Which versions are affected by OSV-2024-177?
1 open source package ship an affected version, including p11-kit.
| Package | Affected | Fixed in |
|---|---|---|
p11-kit OSS-Fuzz | All versions | None |
How do I fix OSV-2024-177?
No fix has been published for OSV-2024-177 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2024-177 being exploited?
There is no known exploitation of OSV-2024-177 in the wild and no public exploit code.