Memory corruption via unchecked .node line count
Published May 28, 2024 · Updated Feb 13, 2025
Out-of-bounds write in libigl 2.5.0 readNODE allows attackers to corrupt process memory by supplying a crafted .node file. The parser sizes its vertex and index matrices from the header point count, then indexes both with an unchecked counter driven by the actual point lines. File processing requires user interaction or equivalent action by a calling application; the demonstrated consequence is memory corruption, not confirmed code execution.
Summary
What happened
Out-of-bounds write in libigl 2.5.0 readNODE allows attackers to corrupt process memory by supplying a crafted .node file. The parser sizes its vertex and index matrices from the header point count, then indexes both with an unchecked counter driven by the actual point lines. File processing requires user interaction or equivalent action by a calling application; the demonstrated consequence is memory corruption, not confirmed code execution.
The record
- CVE
- CVE-2024-22181
- Published
- May 28, 2024
- Updated
- Feb 13, 2025
- Vendor
- libigl
- Product
- libigl
- Classifications
- CWE-787, CWE-129, CAPEC-100, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=v2.5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo