Code execution via unchecked crafted VI
Published Mar 11, 2024 · Updated Aug 22, 2024
Out-of-bounds write in LabVIEW 2024 Q1 and earlier allows local users to execute code by supplying a specially crafted VI. NI attributes the overwrite to missing bounds checks during VI processing but has not identified the affected parser, function, or field. Low-privileged local access is required, and successful exploitation executes attacker-controlled code with the affected process's rights.
Summary
What happened
Out-of-bounds write in LabVIEW 2024 Q1 and earlier allows local users to execute code by supplying a specially crafted VI. NI attributes the overwrite to missing bounds checks during VI processing but has not identified the affected parser, function, or field. Low-privileged local access is required, and successful exploitation executes attacker-controlled code with the affected process's rights.
The record
- CVE
- CVE-2024-23608
- Published
- Mar 11, 2024
- Updated
- Aug 22, 2024
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 11, 2024CVE publishedPublication date reported by the CVE source.
- Aug 22, 2024Record 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.
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