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

> Attackers can cause a Denial of Service in the wac library by submitting a crafted wasm file that triggers a heap overflow.

- **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:** No
- **Published:** 8 Nov 2024
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-wr2h-chhq-3jh8

## What is CVE-2024-35418?

CVE-2024-35418 is a medium-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

wac commit 385e1 was discovered to contain a heap overflow via the setup_call function at /wac-asan/wa.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted wasm file.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Kanaka Wac.

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

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

## Is CVE-2024-35418 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-35410](https://insights.sbomify.com/CVE-2024-35410/): Memory corruption in n/a (medium 6.2)
- [CVE-2024-35420](https://insights.sbomify.com/CVE-2024-35420/): Memory corruption in n/a (medium 6.2)
- [CVE-2024-35419](https://insights.sbomify.com/CVE-2024-35419/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35418 is a medium-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-35418 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-35418/ (Markdown: https://insights.sbomify.com/CVE-2024-35418/index.md)
```

## Sources

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

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