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.

Published: 2024-05-28 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-24684 is rated Moderate Risk (43.6/100): CVSS High severity, with low exploitation likelihood (EPSS 0.74%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-24684

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 21.93% 0.74% -21.18%
2 2025-11-21 12.22% 21.93% +9.70%
3 2025-11-18 — 12.22% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-24684

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2024-24684

OS Trackers for CVE-2024-24684

vendor priority summary link
ubuntu medium CVE-2024-24684 medium priority: Ubuntu including 1 source packages (slic3r-prusa), 9 status rows across 9 suites (bionic, focal, jammy, mantic, noble, oracular, plucky, questing, upstream): needs-triage 6, ignored 3. https://ubuntu.com/security/CVE-2024-24684

Affected software / configurations for CVE-2024-24684

Vendor Product Version Raw CPE
libigl libigl 2.5.0 cpe:2.3:a:libigl:libigl:2.5.0:*:*:*:*:*:*:*

References for CVE-2024-24684

cvelogic Threat Intelligence