# OSV-2021-1061: UNKNOWN WRITE in CompileBlock

> An unknown write vulnerability in CompileBlock can lead to memory corruption, potentially allowing code execution or denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 26 Jul 2021

## What is OSV-2021-1061?

OSV-2021-1061 is a memory corruption vulnerability in wasm3, published on 26 Jul 2021. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=36551

```
Crash type: UNKNOWN WRITE
Crash state:
CompileBlock
CompileElseBlock
Compile_If
```

## Which versions are affected by OSV-2021-1061?

1 open source package ship an affected version, including wasm3.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wasm3` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2021-1061?

No fix has been published for OSV-2021-1061 yet. Limit exposure of the affected software until one is available.

## Is OSV-2021-1061 being exploited?

There is no known exploitation of OSV-2021-1061 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2021-1061 and fix it if it is affected.

What it is: OSV-2021-1061 is a memory corruption vulnerability in wasm3, published on 26 Jul 2021. 
Exploitation: There is no known exploitation of OSV-2021-1061 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-1061/ (Markdown: https://insights.sbomify.com/OSV-2021-1061/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2021-1061

---
From sbomify Insights: https://insights.sbomify.com/OSV-2021-1061/
Summaries are generated and may contain mistakes; the official description above is the record.