Memory corruption via oversized OFF header
Published May 28, 2024 · Updated Feb 13, 2025
Stack-based buffer overflow in libigl 2.5.0 allows context-dependent attackers to corrupt memory via a crafted OFF file. The readOFF header parser passes the file's first whitespace-delimited token to fscanf with an unbounded %s conversion into a fixed 1,000-byte stack buffer. A consuming application must invoke readOFF on the supplied file; the resulting overwrite is confined initially to that application's process.
Summary
What happened
Stack-based buffer overflow in libigl 2.5.0 allows context-dependent attackers to corrupt memory via a crafted OFF file. The readOFF header parser passes the file's first whitespace-delimited token to fscanf with an unbounded %s conversion into a fixed 1,000-byte stack buffer. A consuming application must invoke readOFF on the supplied file; the resulting overwrite is confined initially to that application's process.
The record
- CVE
- CVE-2024-24684
- Published
- May 28, 2024
- Updated
- Feb 13, 2025
- Vendor
- libigl
- Product
- libigl
- Classifications
- CWE-787, CWE-121, T1203
- 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=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.
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