CVE-2023-35951
📋 TL;DR
This vulnerability allows remote code execution through specially crafted .off files in libigl v2.4.0. Attackers can exploit stack-based buffer overflows in the readOFF.cpp parser to execute arbitrary code. Anyone using libigl to process untrusted .off files is affected.
💻 Affected Systems
- libigl
📦 What is this software?
Libigl by Libigl
Libigl by Libigl
⚠️ Risk & Real-World Impact
Worst Case
Full system compromise with attacker gaining the same privileges as the application processing the .off file, potentially leading to data theft, ransomware deployment, or lateral movement.
Likely Case
Application crash (denial of service) or limited code execution within the application's context, potentially leading to data leakage or further exploitation.
If Mitigated
Application crash with no code execution if memory protections (ASLR, DEP) are effective, but denial of service still occurs.
🎯 Exploit Status
Exploitation requires crafting a malicious .off file, but no authentication is needed if the application processes such files. Public PoC exists in Talos advisory.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Version 2.5.0 or later
Vendor Advisory: https://github.com/libigl/libigl/releases
Restart Required: Yes
Instructions:
1. Update libigl to version 2.5.0 or later. 2. Recompile any applications using libigl. 3. Restart affected services.
🔧 Temporary Workarounds
Input validation for .off files
allImplement strict validation of .off file contents before passing to libigl parser
Disable .off file processing
allIf not needed, disable or remove functionality that processes .off files
🧯 If You Can't Patch
- Implement strict file type validation and only accept .off files from trusted sources
- Run the application with minimal privileges and in a sandboxed environment
🔍 How to Verify
Check if Vulnerable:
Check if your application uses libigl version 2.4.0 and processes .off filesCheck Version:
Check build configuration or dependency files for libigl versionVerify Fix Applied:
Verify libigl version is 2.5.0 or later and test with known safe .off files📡 Detection & Monitoring
Log Indicators:
- Application crashes when processing .off files
- Unexpected memory access errors in logs
Network Indicators:
- Unusual .off file uploads to web services
- Large or malformed .off file transfers
SIEM Query:
source="application.log" AND ("segmentation fault" OR "buffer overflow" OR "OFF file")