CVE-2024-24583

What it actually does

Out-of-bounds read in the readMSH function when processing MshLoader::ELEMENT_TRI elements from a crafted .msh file, allowing limited memory disclosure.

Why it matters to the business

Attackers may obtain small amounts of sensitive data by supplying malicious mesh files to applications using the library, requiring user interaction to trigger.

How an attack unfolds

An attacker crafts a .msh file containing malformed ELEMENT_TRI data that triggers the out-of-bounds read during parsing, then convinces a victim to open the file in software linked against the vulnerable library version.

How to fix it

Upgrade libigl to a patched release that correctly bounds ELEMENT_TRI element access in readMSH; recompile dependent applications against the fixed library.

How to confirm the fix worked

Rebuild test harnesses to feed malformed .msh files containing ELEMENT_TRI elements and confirm absence of out-of-bounds accesses or crashes after upgrade.

Typical attack path

1. Generate .msh file with oversized or invalid ELEMENT_TRI element counts
2. Distribute file through email, web download, or shared storage
3. Victim opens file in application using libigl readMSH
4. Parser performs out-of-bounds memory read and returns data to attacker-controlled context

How to detect it

Review application logs and crash reports for unexpected reads or faults while processing .msh files; correlate with file-open events involving untrusted mesh data.

What your security team should do

• Inventory all products and builds that statically or dynamically link libigl
• Schedule upgrade of libigl across the software supply chain
• Add .msh file sanity checks at ingestion points until library is updated