OSV-2021-660 UNKNOWN READ in op_BranchIfPrologue_s
Not scored
Published
Check this codebase for OSV-2021-660 and fix it if it is affected.
What it is: OSV-2021-660 is a memory corruption vulnerability in wasm3, published on 20 Apr 2021.
Exploitation: There is no known exploitation of OSV-2021-660 in the wild and no public exploit code.
Affected packages and fixed versions:
- wasm3 (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-2021-660/ (Markdown: https://insights.sbomify.com/OSV-2021-660/index.md)
An unknown read vulnerability in the WebAssembly runtime can cause a crash, potentially leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2021-660?
OSV-2021-660 is a memory corruption vulnerability in wasm3, published on 20 Apr 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33397
Crash type: UNKNOWN READ
Crash state:
op_BranchIfPrologue_s
m3_CallVL
m3_CallV
Which versions are affected by OSV-2021-660?
1 open source package ship an affected version, including wasm3.
| Package | Affected | Fixed in |
|---|---|---|
wasm3 OSS-Fuzz | All versions | None |
How do I fix OSV-2021-660?
No fix has been published for OSV-2021-660 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-2021-660 being exploited?
There is no known exploitation of OSV-2021-660 in the wild and no public exploit code.