libigl 2.5.0
Approved changes feed: RSS · Atom
cpe:2.3:a:libigl:libigl:2.5.0:*:*:*:*:*:*:*part: a version: 2.5.0 update: *
| Vendor | Libigl (d00b8f0c-2cc1-5639-bea7-85ac075c3654) |
|---|---|
| Product | Libigl (8b8be76f-8d78-5785-a93a-c8053495e846) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/libigl/libigl |
purl2cpe | 2026-06-01 10:17:18.405293 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-24686 |
vulnerable | 2026-06-08 06:29:41.542282 |
Details available
HIGH (7.8)
Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0. A specially crafted .off file can lead to stack-based buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.This vulnerability concerns the parsing of comments within the faces section of an `.off` file processed via the `readOFF` function.
Published: 2024-05-28T14:02:40.153Z
Updated: 2025-02-13T17:40:19.923Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-24685 |
vulnerable | 2026-06-08 06:29:41.540680 |
Details available
HIGH (7.8)
Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0. A specially crafted .off file can lead to stack-based buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.This vulnerability concerns the parsing of comments within the vertex section of an `.off` file processed via the `readOFF` function.
Published: 2024-05-28T14:02:40.055Z
Updated: 2025-02-13T17:40:19.237Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-24684 |
vulnerable | 2026-06-08 06:29:41.540048 |
Details available
HIGH (7.8)
Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0. A specially crafted .off file can lead to stack-based buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.This vulnerability concerns the header parsing occuring while processing an `.off` file via the `readOFF` function.
We can see above that at [0] a stack-based buffer called `comment` is defined with an hardcoded size of `1000 bytes`. The call to `fscanf` at [1] is unsafe and if the first line of the header of the `.off` files is longer than 1000 bytes it will overflow the `header` buffer.
Published: 2024-05-28T14:02:39.939Z
Updated: 2025-02-13T17:40:18.620Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-24584 |
vulnerable | 2026-06-08 06:29:41.520630 |
Details available
MEDIUM (4.3)
Multiple out-of-bounds read vulnerabilities exist in the readMSH functionality of libigl v2.5.0. A specially crafted .msh file can lead to an out-of-bounds read. An attacker can provide a malicious file to trigger this vulnerability.This vulnerabilitty concerns the`readMSH` function while processing `MshLoader::ELEMENT_TET` elements.
Published: 2024-05-28T14:02:40.957Z
Updated: 2025-02-13T17:40:16.104Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-24583 |
vulnerable | 2026-06-08 06:29:41.520338 |
Details available
MEDIUM (4.3)
Multiple out-of-bounds read vulnerabilities exist in the readMSH functionality of libigl v2.5.0. A specially crafted .msh file can lead to an out-of-bounds read. An attacker can provide a malicious file to trigger this vulnerability.This vulnerabilitty concerns the`readMSH` function while processing `MshLoader::ELEMENT_TRI` elements.
Published: 2024-05-28T14:02:40.872Z
Updated: 2025-02-13T17:40:15.459Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-23951 |
vulnerable | 2026-06-08 06:29:40.995568 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-23950 |
vulnerable | 2026-06-08 06:29:40.995111 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-23949 |
vulnerable | 2026-06-08 06:29:40.994675 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-23948 |
vulnerable | 2026-06-08 06:29:40.994109 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-23947 |
vulnerable | 2026-06-08 06:29:40.993582 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-22181 |
vulnerable | 2026-06-08 06:29:34.028051 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-49600 |
vulnerable | 2026-06-08 06:14:29.234737 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-35953 |
vulnerable | 2026-06-08 06:06:28.204272 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-35952 |
vulnerable | 2026-06-08 06:06:28.203898 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-35951 |
vulnerable | 2026-06-08 06:06:28.203543 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-35950 |
vulnerable | 2026-06-08 06:06:28.203111 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-35949 |
vulnerable | 2026-06-08 06:06:28.202629 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.