# CVE-2024-27529: wasm3 uncontrolled memory allocation vulnerability

> Memory leaks in the Read_utf8 function of the wasm3 library can lead to resource exhaustion and denial of service.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Nov 2024
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-fmq6-4w57-2w3v, PYSEC-2024-305

## What is CVE-2024-27529?

CVE-2024-27529 is a high-severity memory corruption vulnerability in n/a, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

wasm3 139076a contains memory leaks in Read_utf8.

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

## Which versions are affected by CVE-2024-27529?

7 open source packages ship an affected version, including pywasm3, github.com/shareup/wasm-interpreter-apple and wasm3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pywasm3` | PyPI | All versions to 0.5.0 | None |
| `pywasm3` | PyPI | All versions to 0.5.0 | None |
| `pywasm3` | PyPI | All versions to 139076a | None |
| `github.com/shareup/wasm-interpreter-apple` | SwiftURL | All versions to 0.8.1 | None |
| `github.com/shareup/wasm-interpreter-apple` | SwiftURL | All versions to 0.8.1 | None |
| `wasm3` | crates.io | All versions to 0.3.1 | None |
| `wasm3` | crates.io | All versions to 0.3.1 | None |

Products: Wasm3 Project Wasm3.

## How do I fix CVE-2024-27529?

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

## Is CVE-2024-27529 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27529 exists.

## 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-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)
- [CVE-2024-27527](https://insights.sbomify.com/CVE-2024-27527/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27529 and fix it if it is affected.

What it is: CVE-2024-27529 is a high-severity memory corruption vulnerability in n/a, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27529 exists.

Affected packages and fixed versions:
- 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
- pywasm3 (PyPI): affected all versions up to 139076a; no fix listed
- github.com/shareup/wasm-interpreter-apple (SwiftURL): affected all versions up to 0.8.1; no fix listed
- github.com/shareup/wasm-interpreter-apple (SwiftURL): affected all versions up to 0.8.1; no fix listed
- wasm3 (crates.io): affected all versions up to 0.3.1; no fix listed
- wasm3 (crates.io): affected all versions up to 0.3.1; 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-2024-27529/ (Markdown: https://insights.sbomify.com/CVE-2024-27529/index.md)
```

## Sources

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

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