OSV-2024-1066 Heap-buffer-overflow in StrLen
Not scored
Published
Check this codebase for OSV-2024-1066 and fix it if it is affected.
What it is: OSV-2024-1066 is a memory corruption vulnerability in edk2, published on 13 Sep 2024.
Exploitation: There is no known exploitation of OSV-2024-1066 in the wild and no public exploit code.
Affected packages and fixed versions:
- edk2 (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-1066/ (Markdown: https://insights.sbomify.com/OSV-2024-1066/index.md)
A heap-buffer-overflow in StrLen within the EDK II firmware library can lead to crashes or potential code execution.
- 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-1066?
OSV-2024-1066 is a memory corruption vulnerability in edk2, published on 13 Sep 2024.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=71496
Crash type: Heap-buffer-overflow READ 2
Crash state:
StrLen
MangleFileName
ToolChainHarnessLib.c
Which versions are affected by OSV-2024-1066?
1 open source package ship an affected version, including edk2.
| Package | Affected | Fixed in |
|---|---|---|
edk2 OSS-Fuzz | All versions | None |
How do I fix OSV-2024-1066?
No fix has been published for OSV-2024-1066 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-1066 being exploited?
There is no known exploitation of OSV-2024-1066 in the wild and no public exploit code.