{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-23948 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-23948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-23948 is a high-severity memory corruption vulnerability in libigl, published on 28 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-23948 and fix it if it is affected.\n\nWhat it is: CVE-2024-23948 is a high-severity memory corruption vulnerability in libigl, published on 28 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-23948 in the wild and no public exploit code.\n\nAffected product: libigl. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-23948/ (Markdown: https://insights.sbomify.com/CVE-2024-23948/index.md)","id":"CVE-2024-23948","markdown":"https://insights.sbomify.com/CVE-2024-23948/index.md","name":"CVE-2024-23948","record":{"aliases":["UBUNTU-CVE-2024-23948"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"libigl geometry library","requires_auth":"none","summary":"An attacker can trigger an out-of-bounds write in libigl by providing a malicious .msh file, potentially leading to code execution or denial of service.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"libigl","vendor":"libigl"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"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 an `ascii`.msh` file.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory corruption in libigl","id":"CVE-2024-23948","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in libigl","id":"CVE-2024-23949"},"packages":[],"prev":{"headline":"Memory corruption in libigl","id":"CVE-2024-23947"},"products":["libigl"],"published":"2024-05-28","related":[{"cvss_score":8.8,"headline":"Memory corruption in libigl","id":"CVE-2024-23947","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":8.8,"headline":"Memory corruption in libigl","id":"CVE-2024-23949","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":8.8,"headline":"Memory corruption in libigl","id":"CVE-2024-23950","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":8.8,"headline":"Memory corruption in libigl","id":"CVE-2024-23951","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":8.1,"headline":"Memory corruption in libigl","id":"CVE-2023-49600","kev_date_added":null,"published":"2024-05-28"},{"cvss_score":7.8,"headline":"Memory corruption in libigl","id":"CVE-2023-35949","kev_date_added":null,"published":"2024-05-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["libigl"]},"summary":"An attacker can trigger an out-of-bounds write in libigl by providing a malicious .msh file, potentially leading to code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2024-23948/"}