Security Resilience

CVE-2024-24686

Memory Safety in Libigl 2.5.0

Published
28 May 2024
Modified
11 February 2025
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0053 43th percentile
Risk Priority 65 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-24686 is a high-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Libigl Libigl. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Security Account Manager (T1003.002); ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2024-24686 is a set of stack-based buffer overflow flaws in the readOFF function of libigl version 2.5.0. The issues occur during parsing of comments inside the faces section of an .off file and are tracked under CWE-121 and CWE-787. Successful exploitation yields a CVSS 7.8 rating reflecting local attack vector, low complexity, no privileges required, and user-interaction dependence with high impact on confidentiality, integrity, and availability.

An attacker can supply a specially crafted .off file that triggers the overflow when the file is opened by an affected application using libigl’s readOFF routine. This grants the ability to corrupt stack memory and potentially execute arbitrary code or crash the process under the privileges of the victim user.

The EPSS score has remained flat at 0.09 with no material increase since disclosure. Public references point to detailed Talos analysis (TALOS-2024-1929) but supply no additional mitigation or patch guidance within the available data.

EU & UK References

Vulnerability Data

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 parsing of…

more

comments within the faces section of an `.off` file processed via the `readOFF` function.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
T1003.004 LSA Secrets Credential Access
Adversaries with SYSTEM access to a host may attempt to access Local Security Authority (LSA) secrets, which can contain a variety of different credential materials, such as credentials for service accounts.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1006 Direct Volume Access Stealth
Adversaries may directly access a volume to bypass file access controls and file system monitoring.
T1007 System Service Discovery Discovery
Adversaries may try to gather information about registered local system services.
T1012 Query Registry Discovery
Adversaries may interact with the Windows Registry to gather information about the system, configuration, and installed software.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-35950Same product: Libigl Libigl
CVE-2024-24684Same product: Libigl Libigl
CVE-2023-35952Same product: Libigl Libigl
CVE-2023-35949Same product: Libigl Libigl
CVE-2024-24685Same product: Libigl Libigl
CVE-2023-35951Same product: Libigl Libigl
CVE-2023-35953Same product: Libigl Libigl
CVE-2025-20736Shared CWE-121, CWE-787
CVE-2023-39276Shared CWE-121, CWE-787
CVE-2024-6402Shared CWE-121, CWE-787

Affected Assets

libigl
libigl
2.5.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and analysis can discover stack-buffer overflows before deployment.

Input validation directly stops untrusted data from exceeding stack buffer bounds.

Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Secure-engineering principles include bounds-checked coding and safe buffer handling that avoid introducing the flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.RA-01 partial match
blocks

Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.

PR.PS-02 partial match
blocks

Patching eliminates known instances of the weakness after discovery.

PR.PS-06 partial match
blocks

Secure-development practices directly prevent introduction of stack buffer overflows.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

removes
removes
removes
removes
removes

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. blocks CWE-121
Oracle Linux 9 (1 rule)
  • V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. blocks CWE-121

References