Code execution via improper bounds checking
Published Jul 23, 2025 · Updated Jul 23, 2025
Out-of-bounds read in lvre!UDecStrToNum in NI LabVIEW 2025 Q1 and earlier allows attackers to disclose data or execute code via a crafted VI. The lvre!UDecStrToNum routine reads outside its intended memory bounds because it fails to validate an input-supplied index, position, or offset. A user must open the file; successful processing exposes process memory or permits code execution in the user's context.
Summary
What happened
Out-of-bounds read in lvre!UDecStrToNum in NI LabVIEW 2025 Q1 and earlier allows attackers to disclose data or execute code via a crafted VI. The lvre!UDecStrToNum routine reads outside its intended memory bounds because it fails to validate an input-supplied index, position, or offset. A user must open the file; successful processing exposes process memory or permits code execution in the user's context.
The record
- CVE
- CVE-2025-2633
- Published
- Jul 23, 2025
- Updated
- Jul 23, 2025
- Vendor
- National Instruments
- Product
- LabVIEW
- Classifications
- CWE-119, CWE-1285, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 23, 2025CVE publishedPublication date reported by the CVE source.
- Jul 23, 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.5
- Affected versionversion=23.0.0 <=23.3.6
- Affected versionversion=24.0.0 <=24.3.3
- Affected versionversion=25.0.0 <25.3.0
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