libigl 2.4.0/2.5.0 OFF File readOFF.cpp stack-based overflow

Summaryinfo

A vulnerability has been found in libigl 2.4.0/2.5.0 and classified as critical. This affects an unknown function of the file readOFF.cpp of the component OFF File Handler. This manipulation causes stack-based overflow. This vulnerability is registered as CVE-2023-35951. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability has been found in libigl 2.4.0/2.5.0 and classified as critical. Affected by this vulnerability is an unknown part of the file readOFF.cpp of the component OFF File Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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 vertices of an OFF file.

It is possible to read the advisory at talosintelligence.com. This vulnerability is known as CVE-2023-35951 since 06/20/2023. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/12/2025).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• libigl

Version

• 2.4.0
• 2.5.0

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion