OSV-2021-698 UNKNOWN READ in m3_Realloc
Not scored
Published
Check this codebase for OSV-2021-698 and fix it if it is affected.
What it is: OSV-2021-698 is a memory corruption vulnerability in wasm3, published on 28 Apr 2021.
Exploitation: There is no known exploitation of OSV-2021-698 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-698/ (Markdown: https://insights.sbomify.com/OSV-2021-698/index.md)
An unknown read error in the m3_Realloc function can cause a crash, potentially leading to denial of service in applications using this WebAssembly runtime.
- 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-698?
OSV-2021-698 is a memory corruption vulnerability in wasm3, published on 28 Apr 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=33744
Crash type: UNKNOWN READ
Crash state:
m3_Realloc
InitMemory
CompileBlockStatements
Which versions are affected by OSV-2021-698?
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-698?
No fix has been published for OSV-2021-698 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-698 being exploited?
There is no known exploitation of OSV-2021-698 in the wild and no public exploit code.