CVE-2025-64466

7.8 HIGH

📋 TL;DR

An out-of-bounds read vulnerability in NI LabVIEW's lvre!ExecPostedProcRecPost() function when parsing corrupted VI files could lead to information disclosure or arbitrary code execution. Attackers must trick users into opening specially crafted VI files. This affects NI LabVIEW 2025 Q3 (25.3) and earlier versions.

💻 Affected Systems

Products:
  • NI LabVIEW
Versions: 2025 Q3 (25.3) and prior versions
Operating Systems: Windows, Linux, macOS
Default Config Vulnerable: ⚠️ Yes
Notes: All LabVIEW installations within affected version range are vulnerable when opening VI files.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Arbitrary code execution with the privileges of the LabVIEW user, potentially leading to full system compromise.

🟠

Likely Case

Information disclosure through memory leaks or application crashes when users open malicious VI files.

🟢

If Mitigated

Limited impact if users only open trusted VI files from verified sources.

🌐 Internet-Facing: LOW - Requires user interaction with malicious files, not directly exploitable over network.
🏢 Internal Only: MEDIUM - Internal users could be targeted via phishing or shared malicious VI files.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires user interaction to open malicious VI file. No public exploit code available at this time.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: NI LabVIEW 2025 Q4 (25.4) or later

Vendor Advisory: https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/multiple-memory-corruption-vulnerabilities-in-ni-labview.html

Restart Required: Yes

Instructions:

1. Download and install NI LabVIEW 2025 Q4 (25.4) or later from NI website. 2. Restart the system after installation. 3. Verify the update was successful by checking the LabVIEW version.

🔧 Temporary Workarounds

Restrict VI file execution

all

Configure application control policies to restrict execution of VI files from untrusted sources.

User awareness training

all

Train users to only open VI files from trusted sources and verify file integrity.

🧯 If You Can't Patch

  • Implement strict file validation policies to block VI files from untrusted sources
  • Use application sandboxing or virtualization to isolate LabVIEW execution

🔍 How to Verify

Check if Vulnerable:

Check LabVIEW version via Help > About LabVIEW. If version is 25.3 or earlier, system is vulnerable.

Check Version:

On Windows: Check Help > About LabVIEW in the application. Command line: Not available.

Verify Fix Applied:

Verify LabVIEW version is 25.4 or later via Help > About LabVIEW after patch installation.

📡 Detection & Monitoring

Log Indicators:

  • LabVIEW crash logs with memory access violations
  • Unexpected process termination of LabVIEW.exe

Network Indicators:

  • Unusual file transfers of VI files via email or network shares

SIEM Query:

EventID=1000 OR EventID=1001 AND ProcessName="LabVIEW.exe" AND (ExceptionCode=0xc0000005 OR ExceptionCode=0xc0000409)

🔗 References

📤 Share & Export