dbcve.org
LibiglApplication

CVE-2024-23947

HIGH · 8.8 CVSS v3.1 Published 2024-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple improper array index validation vulnerabilities exist in the readMSH functionality of libigl v2.5.0. A specially crafted .msh file can lead to an out-of-bounds write. An attacker can provide a malicious file to trigger this vulnerability.This vulnerability concerns the `igl::MshLoader::parse_nodes` function while handling a `binary` `.msh` file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple improper array index validation vulnerabilities exist in the `igl::MshLoader::parse_nodes` function of libigl v2.5.0 when parsing binary .msh files. The parser fails to validate array indices before use, allowing an attacker-provided malicious file to trigger out-of-bounds memory writes.

MitigationUpdate to a patched version of libigl that adds proper bounds checking on array indices in the MshLoader::parse_nodes function, or implement input validation to verify all array indices are within valid bounds before memory access operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LibiglApplication
Affected:= 2.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify libigl version
    Locate the libigl version header (typically version.h or Version.h in the include directory) or check CMakeLists.txt for the version definition. Compare against the affected version 2.5.0.
    Affected if Running libigl version 2.5.0 exactly
  2. Verify MshLoader module is compiled
    Search project source files for #include <igl/MshLoader.h> or usage of igl::MshLoader class to confirm the MshLoader module is included in the build.
    Affected if MshLoader module is compiled and linked into the application
  3. Check for .msh file loading code
    Search source code for calls to MshLoader::read or methods that load .msh files, particularly binary format .msh files.
    Affected if Application code loads .msh files using MshLoader
  4. Inspect parse_nodes implementation
    Examine the igl::MshLoader::parse_nodes function source code in MshLoader.cpp for presence of array index validation before array access operations.
    Affected if parse_nodes function lacks proper bounds checking on array indices before use

Environment is affected if running libigl version 2.5.0, compiling the MshLoader module, and processing binary .msh files where parse_nodes does not validate array indices before accessing them.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of libigl that adds proper bounds checking on array indices in the MshLoader::parse_nodes function, or implement input validation to verify all array indices are within valid bounds before memory access operations.

Recommended fix Moderate confidence

latest stable libigl release (check github.com/libigl/libigl for current version after fix)

  1. 1. Obtain the latest stable release of Libigl from the official repository (github.com/libigl/libigl)
  2. 2. Review the Libigl release notes or changelog to confirm the version includes a fix for CVE-2024-23947
  3. 3. Replace the vulnerable libigl v2.5.0 installation with the newer version
  4. 4. Recompile any projects that depend on libigl against the updated version
  5. 5. Test the readMSH functionality with both ASCII and binary .msh files to verify the vulnerability is remediated
Caveat Review changelog for any API changes between v2.5.0 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Libigl Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23947 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data