CVE-2023-35953

What it actually does

Stack-based buffer overflow in libigl readOFF.cpp during comment parsing inside the geometric vertices section of an OFF file, enabling arbitrary code execution when a malformed file is processed.

Why it matters to the business

Attackers could execute malicious code on systems that open crafted geometry files, leading to unauthorized access, data theft, or disruption of design and simulation workflows that rely on the library.

How an attack unfolds

An attacker creates a specially crafted OFF file containing an oversized comment within the vertices section. When a victim application using the vulnerable libigl library opens the file, the parsing routine overflows the stack buffer and allows the attacker to control execution flow for code execution.

How to fix it

Upgrade libigl to a version containing the corrected readOFF.cpp parsing logic. Validate the update by confirming the library version and testing file ingestion with known-good OFF files.

How to confirm the fix worked

Confirm the installed libigl version is newer than 2.4.0 and that the readOFF.cpp changes addressing comment buffer handling are present. Reprocess a set of test OFF files containing comments to ensure no crashes or unexpected behavior occur.

Typical attack path

1. Craft a malicious OFF file that triggers the buffer overflow in comment parsing
2. Deliver the file to the target via email, download link, or shared storage
3. Victim opens the file using software linked against the vulnerable libigl version
4. Overflow occurs during vertices section processing, leading to arbitrary code execution

How to detect it

Review application logs for crashes or errors during OFF file parsing. Search process execution and file-access logs for unexpected child processes spawned while handling .off files. Correlate with user activity around geometry file ingestion.

What your security team should do

• Identify all applications and build pipelines that depend on libigl and schedule immediate upgrades
• Add file-type validation and sandboxing for OFF file processing until patches are applied
• Monitor vulnerability feeds for any future public exploits targeting this parsing flaw