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

> A heap buffer overflow in the vmir WASM parser allows attackers to execute arbitrary code or cause denial of service via crafted WASM files.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Nov 2024
- **Updated:** 14 Mar 2025
- **Also known as:** GHSA-whgf-6h8c-97q6

## What is CVE-2024-35422?

CVE-2024-35422 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, and only if a user opens a file or follows a link.

### Official description

vmir e8117 was discovered to contain a heap buffer overflow via the wasm_call function at /src/vmir_wasm_parser.c.

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

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

It affects 1 product.


Products: Lonelycoder Vmir.

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

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

## Is CVE-2024-35422 being exploited?

There is no known exploitation of CVE-2024-35422 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-35426](https://insights.sbomify.com/CVE-2024-35426/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-35423](https://insights.sbomify.com/CVE-2024-35423/): Memory corruption in n/a (high 7.8)
- [CVE-2024-35421](https://insights.sbomify.com/CVE-2024-35421/): Null dereference in n/a (medium 5.5)
- [CVE-2024-35424](https://insights.sbomify.com/CVE-2024-35424/): Null dereference in n/a (medium 5.5)
- [CVE-2024-35425](https://insights.sbomify.com/CVE-2024-35425/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35422 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, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-35422 in the wild and no public exploit code.

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

## Sources

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

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