# CVE-2024-22181: Memory corruption in libigl

> An attacker can trigger an out-of-bounds write in libigl by providing a malicious .node file, potentially leading to code execution or crashes.

- **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:** 28 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** UBUNTU-CVE-2024-22181

## What is CVE-2024-22181?

CVE-2024-22181 is a high-severity memory corruption vulnerability in libigl, published on 28 May 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

An out-of-bounds write vulnerability exists in the readNODE functionality of libigl v2.5.0. A specially crafted .node file can lead to an out-of-bounds write. An attacker can provide a malicious file to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-129 (Improper Validation of Array Index)

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

It affects 1 product.


Products: Libigl Libigl.

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

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

## Is CVE-2024-22181 being exploited?

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

## Other vulnerabilities in libigl

- [CVE-2024-23947](https://insights.sbomify.com/CVE-2024-23947/): Memory corruption in libigl (high 8.8)
- [CVE-2024-23948](https://insights.sbomify.com/CVE-2024-23948/): Memory corruption in libigl (high 8.8)
- [CVE-2024-23949](https://insights.sbomify.com/CVE-2024-23949/): Memory corruption in libigl (high 8.8)
- [CVE-2024-23950](https://insights.sbomify.com/CVE-2024-23950/): Memory corruption in libigl (high 8.8)
- [CVE-2024-23951](https://insights.sbomify.com/CVE-2024-23951/): Memory corruption in libigl (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22181 is a high-severity memory corruption vulnerability in libigl, published on 28 May 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-22181 in the wild and no public exploit code.

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

## Sources

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

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