Code execution via VI file parser buffer overwrite
Published Mar 11, 2024 · Updated Aug 8, 2024
Out-of-bounds write in National Instruments LabVIEW 2024 Q1 and earlier allows context-dependent attackers to execute code via a crafted VI file. The VI file parser insufficiently validates user-supplied length or offset data, allowing a write past the end of an allocated buffer. Exploitation requires a user to open the malicious file or visit content that delivers it, and resulting code runs in the LabVIEW process context.
Summary
What happened
Out-of-bounds write in National Instruments LabVIEW 2024 Q1 and earlier allows context-dependent attackers to execute code via a crafted VI file. The VI file parser insufficiently validates user-supplied length or offset data, allowing a write past the end of an allocated buffer. Exploitation requires a user to open the malicious file or visit content that delivers it, and resulting code runs in the LabVIEW process context.
The record
- CVE
- CVE-2024-23610
- Published
- Mar 11, 2024
- Updated
- Aug 8, 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 8, 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