# CVE-2024-34250: Memory corruption in n/a

> A heap buffer overflow in the wasm-micro-runtime library allows remote attackers to cause a denial of service.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-40393, AZL-40433, GHSA-7wfw-7p9h-4j2c

## What is CVE-2024-34250?

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

### Official description

A heap buffer overflow vulnerability was discovered in Bytecode Alliance wasm-micro-runtime v2.0.0 which allows a remote attacker to cause at least a denial of service via the "wasm_loader_check_br" function in core/iwasm/interpreter/wasm_loader.c.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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

It affects 1 product.


Products: Bytecodealliance Webassembly Micro Runtime.

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

Upgrade to a fixed version.

## Is CVE-2024-34250 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-25431](https://insights.sbomify.com/CVE-2024-25431/): Memory corruption in n/a (high 8.8)
- [CVE-2024-27532](https://insights.sbomify.com/CVE-2024-27532/): Null dereference in n/a (high 7.5)
- [CVE-2024-34251](https://insights.sbomify.com/CVE-2024-34251/): Memory corruption in n/a (high 7.5)
- [CVE-2023-48105](https://insights.sbomify.com/CVE-2023-48105/): Memory corruption in n/a (high 7.5)
- [CVE-2025-43853](https://insights.sbomify.com/CVE-2025-43853/): iwasm vulnerable to filesystem sandbox escape with symlink when using uvwasi feature (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-34250 is a medium-severity memory corruption vulnerability in n/a, published on 6 May 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-34250 exists.

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

## Sources

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

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