# CVE-2022-34529: WASM3 segmentation fault

> A segmentation fault in the WASM3 library allows attackers to cause a denial of service via the Compile_Memory_CopyFill component.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gq4p-4hxv-5rg9, PYSEC-2022-43057

## What is CVE-2022-34529?

CVE-2022-34529 is a medium-severity vulnerability in n/a, published on 27 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

WASM3 v0.5.0 was discovered to contain a segmentation fault via the component Compile_Memory_CopyFill.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-34529?

5 open source packages ship an affected version, including pywasm3 and wasm3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pywasm3` | PyPI | All versions | None |
| `pywasm3` | PyPI | All versions to 0.5.0 | None |
| `pywasm3` | PyPI | All versions to 0.5.0 | None |
| `wasm3` | crates.io | All versions to 0.5.0 | None |
| `wasm3` | crates.io | All versions to 0.5.0 | None |

Products: Wasm3 Project Wasm3.

## How do I fix CVE-2022-34529?

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

## Is CVE-2022-34529 being exploited?

There is no known exploitation of CVE-2022-34529 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-2022-34529 and fix it if it is affected.

What it is: CVE-2022-34529 is a medium-severity vulnerability in n/a, published on 27 Jul 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-34529 in the wild and no public exploit code.

Affected packages and fixed versions:
- pywasm3 (PyPI): affected all versions; no fix listed
- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed
- pywasm3 (PyPI): affected all versions up to 0.5.0; no fix listed
- wasm3 (crates.io): affected all versions up to 0.5.0; no fix listed
- wasm3 (crates.io): affected all versions up to 0.5.0; 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/CVE-2022-34529/ (Markdown: https://insights.sbomify.com/CVE-2022-34529/index.md)
```

## Sources

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

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