CVE-2024-24684 Memory corruption in libigl
A stack-based buffer overflow in libigl allows attackers to execute arbitrary code by providing a maliciously crafted .off file.
- 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
- None listed
What is CVE-2024-24684?
CVE-2024-24684 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
Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0. A specially crafted .off file can lead to stack-based buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.This vulnerability concerns the header parsing occuring while processing an `.off` file via the `readOFF` function. We can see above that at [0] a stack-based buffer called `comment` is defined with an hardcoded size of `1000 bytes`. The call to `fscanf` at [1] is unsafe and if the first line of the header of the `.off` files is longer than 1000 bytes it will overflow the `header` buffer.
Which versions are affected by CVE-2024-24684?
It affects 1 product.
Products include Libigl Libigl.
How do I fix CVE-2024-24684?
No fix has been published for CVE-2024-24684 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2024-24684 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-24684 exists.
Public exploit code: 1 proofs of concept on GitHub.
Other vulnerabilities in libigl
Sources
Also known as UBUNTU-CVE-2024-24684.