Skip to content
Noroxi
CVE-2023-35949· NVD / CVE Program· CNA talos

Multiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0.

Multiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0. A specially-crafted .off file can lead to a buffer overflow. An attacker can arbitrary code execution to trigger these vulnerabilities.This vulnerability exists within the code responsible for parsing geometric faces of an OFF file.

HighCVSS 7.8 · v3.1—No exploit No fix recorded
Published
May 28, 2024
Updated
Jun 17, 2026
EPSS
0.5% · 40th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · talos
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
libigllibigl

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • libigl libigl2.4.0
  • libigl libigl2.5.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (talos). Independent of NVD's CPE analysis and usually ahead of it.

  • libigl libigl

    • v2.4.0, v2.5.0affected

Other highest-scoring records for the same primary product.

  • CVE-2024-23951Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0.
    35Monitor
  • CVE-2024-23950Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0.
    35Monitor
  • CVE-2024-23949Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0.
    35Monitor
  • CVE-2024-23948Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0.
    35Monitor
  • CVE-2024-23947Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0.
    35Monitor
  • CVE-2024-24686Multiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0.
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-359500 days apartMultiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0.
    31Monitor
  • CVE-2023-359510 days apartMultiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0.
    31Monitor
  • CVE-2023-359520 days apartMultiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0.
    31Monitor
  • CVE-2023-359530 days apartMultiple stack-based buffer overflow vulnerabilities exist in the readOFF.cpp functionality of libigl v2.4.0.
    31Monitor
  • CVE-2024-246850 days apartMultiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0.
    31Monitor
  • CVE-2024-246860 days apartMultiple stack-based buffer overflow vulnerabilities exist in the readOFF functionality of libigl v2.5.0.
    31Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records