CVE-2023-49600

CVE-2023-49600 is a high-severity vulnerability in Libigl with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-787.

Key facts

Description

An out-of-bounds write vulnerability exists in the PlyFile ply_cast_ascii functionality of libigl v2.5.0. A specially crafted .ply file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.

Frequently asked questions

What is CVE-2023-49600?
An out-of-bounds write vulnerability exists in the PlyFile ply_cast_ascii functionality of libigl v2.5.0. A specially crafted .ply file can lead to a heap buffer overflow. An attacker can provide a malicious file to trigger this vulnerability.
How severe is CVE-2023-49600?
CVE-2023-49600 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2023-49600 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (47th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2023-49600?
CVE-2023-49600 affects Libigl. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2023-49600?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2023-49600 have an EU (EUVD) identifier?
Yes. CVE-2023-49600 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2023-53548.
When was CVE-2023-49600 published?
CVE-2023-49600 was published on 2024-05-28 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Libigl

All CVEs affecting Libigl →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →