# CVE-2021-38592: Memory corruption in n/a

> A heap-based buffer overflow in Wasm3 allows attackers to execute arbitrary code or cause denial of service via crafted WebAssembly modules.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-w873-jf59-8229

## What is CVE-2021-38592?

CVE-2021-38592 is a high-severity memory corruption vulnerability in n/a, published on 12 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wasm3 0.5.0 has a heap-based buffer overflow in op_Const64 (called from EvaluateExpression and m3_LoadModule).

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2021-38592?

It affects 1 product.


Products: Wasm3 Project Wasm3.

## How do I fix CVE-2021-38592?

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

## Is CVE-2021-38592 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-34249](https://insights.sbomify.com/CVE-2024-34249/): pywasm3 contains a heap buffer overflow which leads to segmentation fault (critical 9.8)
- [CVE-2024-27528](https://insights.sbomify.com/CVE-2024-27528/): pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution (high 8.4)
- [CVE-2024-27529](https://insights.sbomify.com/CVE-2024-27529/): wasm3 uncontrolled memory allocation vulnerability (high 8.4)
- [CVE-2024-27530](https://insights.sbomify.com/CVE-2024-27530/): pywasm3 contains a Use-After-Free in ForEachModule (high 8.4)
- [CVE-2022-28990](https://insights.sbomify.com/CVE-2022-28990/): Buffer overflow in wasm3 (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38592 and fix it if it is affected.

What it is: CVE-2021-38592 is a high-severity memory corruption vulnerability in n/a, published on 12 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-38592 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2021-38592/ (Markdown: https://insights.sbomify.com/CVE-2021-38592/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-38592
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-38592
- OSV: https://osv.dev/vulnerability/CVE-2021-38592

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