OSV-2024-221 Heap-buffer-overflow in libspdm_copy_mem
Not scored
Published
Check this codebase for OSV-2024-221 and fix it if it is affected.
What it is: OSV-2024-221 is a memory corruption vulnerability in libspdm, published on 31 Mar 2024.
Exploitation: There is no known exploitation of OSV-2024-221 in the wild and no public exploit code.
Affected packages and fixed versions:
- libspdm (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-221/ (Markdown: https://insights.sbomify.com/OSV-2024-221/index.md)
A heap-buffer-overflow in libspdm_copy_mem allows attackers to cause denial of service or potentially execute code via crafted SPDM messages.
- 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-221?
OSV-2024-221 is a memory corruption vulnerability in libspdm, published on 31 Mar 2024.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=67585
Crash type: Heap-buffer-overflow READ 1
Crash state:
libspdm_copy_mem
libspdm_get_response_chunk_send
libspdm_get_response_chunk_send
Which versions are affected by OSV-2024-221?
1 open source package ship an affected version, including libspdm.
| Package | Affected | Fixed in |
|---|---|---|
libspdm OSS-Fuzz | All versions | None |
How do I fix OSV-2024-221?
No fix has been published for OSV-2024-221 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-221 being exploited?
There is no known exploitation of OSV-2024-221 in the wild and no public exploit code.