CVE-2024-24685: Libigl Buffer Overflow Vulnerability

CVE-2024-24685 Overview

CVE-2024-24685 is a stack-based buffer overflow vulnerability in the readOFF functionality of libigl v2.5.0, a C++ geometry processing library. The flaw affects how the parser processes comments within the vertex section of .off mesh files. An attacker who convinces a user to open a specially crafted .off file can trigger memory corruption on the stack. Successful exploitation can lead to arbitrary code execution in the context of the application embedding libigl. The vulnerability was reported by Cisco Talos and tracked as TALOS-2024-1929. It is classified under [CWE-121] Stack-based Buffer Overflow and [CWE-787] Out-of-bounds Write.

Critical Impact
A malicious .off file processed by readOFF can corrupt the stack and enable local code execution with the privileges of the target user.

Affected Products

libigl libigl 2.5.0
Applications and tools embedding the vulnerable readOFF parser
Downstream geometry processing pipelines consuming untrusted .off files

Discovery Timeline

2024-05-28 - CVE-2024-24685 published to the National Vulnerability Database (NVD)
2026-06-17 - Last updated in NVD database

Technical Details for CVE-2024-24685

Vulnerability Analysis

The vulnerability resides in libigl's readOFF function, which parses Object File Format (.off) mesh files. During processing of the vertex section, the parser handles inline comments using fixed-size stack buffers. Comment content that exceeds those buffers is copied without adequate length validation, producing an out-of-bounds write on the stack. Because the write occurs on the stack frame of the parsing routine, saved return addresses and adjacent local variables can be overwritten. Exploitation requires user interaction: the victim must open or import a crafted .off file into an application built against libigl v2.5.0. The impact spans confidentiality, integrity, and availability, since arbitrary code execution in the parsing process is achievable.

Root Cause

The root cause is missing bounds validation while copying comment data during vertex section parsing in readOFF. Fixed-size stack buffers are used as destinations for content whose length is controlled by the input file. This pattern maps to [CWE-121] and [CWE-787], where attacker-controlled input drives an out-of-bounds write on the stack.

Attack Vector

The attack vector is local and requires user interaction. An attacker crafts a malicious .off file with oversized or malformed comments inside the vertex section. The victim opens the file with an application that uses libigl's readOFF. Parsing triggers the stack overflow, potentially leading to code execution under the victim's account.

No public proof-of-concept exploit is listed in the enriched data, and CISA has not added this CVE to the Known Exploited Vulnerabilities catalog. Refer to the Talos Intelligence Vulnerability Report for full technical analysis.

Detection Methods for CVE-2024-24685

Indicators of Compromise

Unexpected crashes or abnormal termination in processes that load .off files through libigl.
Presence of .off files from untrusted sources in engineering, CAD, or research workflows.
Stack corruption signatures such as __stack_chk_fail aborts or access violations inside readOFF frames.

Detection Strategies

Hunt for processes linking libigl that terminate abnormally while reading files with .off extensions.
Inspect .off files for overly long comment lines embedded in the vertex section prior to ingestion.
Deploy file-type-aware content inspection at email and file-sharing gateways to flag anomalous .off payloads.

Monitoring Recommendations

Enable process crash telemetry and core dump collection on workstations that handle geometry files.
Alert on child process creation or shell spawning from applications that embed libigl parsers.
Correlate file writes of .off artifacts with subsequent execution anomalies in EDR telemetry.

How to Mitigate CVE-2024-24685

Immediate Actions Required

Identify all applications, plugins, and internal tools that statically or dynamically link libigl v2.5.0.
Restrict opening of .off files to trusted, internally generated sources until a fixed build is deployed.
Run applications that parse untrusted mesh files inside sandboxed or least-privilege user contexts.

Patch Information

As of the last NVD update, the enriched data lists no vendor advisory URL or fixed release. Consumers should track the libigl upstream repository and the Talos Intelligence Vulnerability Report for patch availability. Once a fixed version is released, rebuild and redistribute all downstream binaries that statically link libigl.

Workarounds

Pre-validate .off files with a lightweight sanitizer that rejects comments exceeding a conservative byte limit before invoking readOFF.
Convert untrusted .off inputs to another mesh format using a hardened, out-of-process converter running under reduced privileges.
Enable compiler hardening flags such as -fstack-protector-strong, -D_FORTIFY_SOURCE=2, and ASLR when rebuilding applications that link libigl.

bash

# Configuration example: rebuild libigl consumers with stack hardening
export CFLAGS="-O2 -fstack-protector-strong -D_FORTIFY_SOURCE=2 -fPIE"
export CXXFLAGS="$CFLAGS"
export LDFLAGS="-Wl,-z,relro,-z,now -pie"
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build --parallel