# CVE-2024-27532: Null dereference in n/a

> A NULL pointer dereference in the WebAssembly Micro Runtime allows attackers to cause a denial of service.

- **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:** Yes
- **Published:** 8 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** AZL-52557, AZL-52586, GHSA-7h2g-q5x6-pwg2

## What is CVE-2024-27532?

CVE-2024-27532 is a high-severity vulnerability in n/a, published on 8 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

wasm-micro-runtime (aka WebAssembly Micro Runtime or WAMR) 06df58f is vulnerable to NULL Pointer Dereference in function `block_type_get_result_types.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Bytecodealliance Webassembly Micro Runtime.

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

Apply the vendor's patch.

## Is CVE-2024-27532 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27532 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-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)
- [CVE-2025-54126](https://insights.sbomify.com/CVE-2025-54126/): WebAssembly Micro Runtime's `--addr-pool` option allows all IPv4 addresses when subnet mask is not specified (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27532 is a high-severity vulnerability in n/a, published on 8 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27532 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-27532/ (Markdown: https://insights.sbomify.com/CVE-2024-27532/index.md)
```

## Sources

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

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