Buffer overflow in Libigl
CVE-2024-24684
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.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.008, 55.6th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Libigl — versions 2.5.0, v2.5.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- SpiralBL0CK/CVE-2024-24684 (last pushed 2024-10-15): Crash File ( Poc for CVE-2024-24684)
Also mentioned in 1 other repository (nomi-sec/PoC-in-GitHub). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://talosintelligence.com/vulnerability_reports/TALOS-2024-1929 (Third Party Advisory, Mitigation)
- www.talosintelligence.com/vulnerability_reports/TALOS-2024-1929 (Third Party Advisory, Mitigation)
This CVE has public exploit evidence. See the latest CVEs with public exploits.