Code execution via InitCPUInformation bounds error
Published Apr 9, 2025 · Updated Apr 9, 2025
Out-of-bounds write in InitCPUInformation() in NI LabVIEW 2025 Q1 and earlier allows attackers to execute code via a crafted VI. InitCPUInformation() performs improper bounds checking while processing VI data and writes beyond the intended buffer. Exploitation requires a local user to open the file, and successful memory corruption can disclose information or run attacker-controlled code.
Summary
What happened
Out-of-bounds write in InitCPUInformation() in NI LabVIEW 2025 Q1 and earlier allows attackers to execute code via a crafted VI. InitCPUInformation() performs improper bounds checking while processing VI data and writes beyond the intended buffer. Exploitation requires a local user to open the file, and successful memory corruption can disclose information or run attacker-controlled code.
The record
- CVE
- CVE-2025-2631
- Published
- Apr 9, 2025
- Updated
- Apr 9, 2025
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2025CVE publishedPublication date reported by the CVE source.
- Apr 9, 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 <22.3.4
- Affected versionversion=23.1.0 <23.3.5
- Affected versionversion=24.1.0 <24.3.2
- Affected versionversion=25.1.0 <25.1.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