Stack-based Buffer Overflow Vulnerability in NI I/O Trace Tool

published 2024-07-23 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-46787

cvss: 7.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-24-205-01 updated 2024-07-23 cvss 7.8

National Instruments IO Trace

National Instruments I/O TRACE
affected: mitigation “National Instruments has provided a fix for this issue and recommends users refer to their public advisory.” ni.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-07-23)

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.8	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

NI IO Trace Tool
ni system_configuration

Classification

Weakness

CWE-121 Stack-based Buffer Overflow

References

ni.com /en/support/security/available-critical-and-security-updates-for-ni-software/stack-based-buffer-overflow-vulne

Sources

CVE List CVE-2024-5602
NVD CVE-2024-5602

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary