Code execution via crafted VI length corruption
Published Jul 23, 2024 · Updated Sep 30, 2025
Memory corruption in National Instruments LabVIEW 2024 Q1 and earlier allows attackers to disclose information or execute code via a crafted VI. LabVIEW processes attacker-controlled length data without an adequate bounds check when a VI is opened, but NI has not disclosed the affected parser, function, or buffer operation. Exploitation requires a user to open the malicious VI locally; successful corruption can expose process memory or execute code in the user's context.
Summary
What happened
Memory corruption in National Instruments LabVIEW 2024 Q1 and earlier allows attackers to disclose information or execute code via a crafted VI. LabVIEW processes attacker-controlled length data without an adequate bounds check when a VI is opened, but NI has not disclosed the affected parser, function, or buffer operation. Exploitation requires a user to open the malicious VI locally; successful corruption can expose process memory or execute code in the user's context.
The record
- CVE
- CVE-2024-4081
- Published
- Jul 23, 2024
- Updated
- Sep 30, 2025
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-119, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2024CVE publishedPublication date reported by the CVE source.
- Sep 30, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=24.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo