Arbitrary code execution via VI parser out-of-bounds write
Published Mar 11, 2024 · Updated Apr 16, 2025
Out-of-bounds write in LabVIEW 2024 Q1 and earlier allows remote attackers to execute code when a user opens a crafted VI file. The VI file parser fails to validate user-supplied data and writes past the end of an allocated data structure. Exploitation requires user interaction and runs code in the context of the LabVIEW process.
Summary
What happened
Out-of-bounds write in LabVIEW 2024 Q1 and earlier allows remote attackers to execute code when a user opens a crafted VI file. The VI file parser fails to validate user-supplied data and writes past the end of an allocated data structure. Exploitation requires user interaction and runs code in the context of the LabVIEW process.
The record
- CVE
- CVE-2024-23609
- Published
- Mar 11, 2024
- Updated
- Apr 16, 2025
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-755, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Apr 16, 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 <=2024_q1
- Affected versionversion=0 <=2024 Q1
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