NI IO Trace Tool up to 24.3 Nitrace File stack-based overflow

Summaryinfo

A vulnerability marked as critical has been reported in NI IO Trace Tool up to 24.3. Affected by this vulnerability is an unknown functionality of the component Nitrace File Handler. Performing a manipulation results in stack-based overflow. This vulnerability was named CVE-2024-5602. The attack needs to be approached locally. There is no available exploit.

Detailsinfo

A vulnerability was found in NI IO Trace Tool up to 24.3. It has been classified as critical. This affects an unknown code of the component Nitrace File Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as 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). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A stack-based buffer overflow vulnerability due to a missing bounds check in the NI I/O Trace Tool may result in arbitrary code execution. Successful exploitation requires an attacker to provide a user with a specially crafted nitrace file. The NI I/O Trace tool is installed as part of the NI System Configuration utilities included with many NI software products.  Refer to the NI Security Advisory for identifying the version of NI IO Trace.exe installed. The NI I/O Trace tool was also previously released as NI Spy.

The weakness was presented by Michael Heinzl. It is possible to read the advisory at ni.com. This vulnerability is uniquely identified as CVE-2024-5602 since 06/03/2024. The exploitability is told to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/24/2024).

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

Vendor

• NI

Name

• IO Trace Tool

Version

• 24.0
• 24.1
• 24.2
• 24.3

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