Memory corruption via unchecked MSH node index
Published May 28, 2024 · Updated Feb 13, 2025
Out-of-bounds write in libigl 2.5.0 allows attackers to corrupt memory by supplying a crafted ASCII .msh file to a consuming application. The parse_nodes function subtracts one from an attacker-controlled node index and uses it to address m_nodes without a bounds check. A user must cause a consuming application to parse the file; the overwrite corrupts memory within that application's process.
Summary
What happened
Out-of-bounds write in libigl 2.5.0 allows attackers to corrupt memory by supplying a crafted ASCII .msh file to a consuming application. The parse_nodes function subtracts one from an attacker-controlled node index and uses it to address m_nodes without a bounds check. A user must cause a consuming application to parse the file; the overwrite corrupts memory within that application's process.
The record
- CVE
- CVE-2024-23948
- Published
- May 28, 2024
- Updated
- Feb 13, 2025
- Vendor
- libigl
- Product
- libigl
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- 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=2.5.0
- 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.
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