dbcve.org
LabviewApplication · Ni

CVE-2024-23612

HIGH · 7.8 CVSS v3.1 Published 2024-03-11
Fix available
A fix is available. Upgrade to after 2020 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An improper error handling vulnerability in LabVIEW may result in remote code execution. Successful exploitation requires an attacker to provide a user with a specially crafted VI. This vulnerability affects LabVIEW 2024 Q1 and prior versions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An improper error handling vulnerability in LabVIEW allows remote code execution when a user opens a specially crafted VI (Virtual Instrument) file. The vulnerability stems from insufficient validation and error handling during VI file parsing, enabling an attacker to execute arbitrary code via the malicious file.

MitigationAvoid opening VI files from untrusted or unverified sources. Apply vendor patches from National Instruments when released. Implement application whitelisting and endpoint protection to mitigate risks from malicious file execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LabviewApplication
Affected:<= 2020= 2021= 2022= 2023= 2024

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed LabVIEW version
    Check the LabVIEW installation or program files for version information, or use system inventory tools to enumerate installed National Instruments software
    Affected if The installed version matches any of these: 2020 (any update <=2020), 2021, 2022, 2023, or 2024 (all subversions)
  2. Confirm LabVIEW is actively installed
    Verify LabVIEW executable (typically labview.exe) exists in the Program Files directory or equivalent, and the application is operational on the system
    Affected if LabVIEW is installed and runnable on the system
  3. Check if .vi file associations are enabled
    Inspect system file type associations to confirm .vi files are linked to LabVIEW, or verify LabVIEW can open VI files as a file handler
    Affected if The system can open or parse .vi files through LabVIEW
  4. Assess user ability to open external VI files
    Determine if standard users can double-click VI files to launch LabVIEW and load them, or if LabVIEW accepts VI files as drag-and-drop input
    Affected if Users can open arbitrary VI files from any location without explicit security warnings
  5. Review application execution controls
    Check if application whitelisting or endpoint protection policies are in place that could restrict LabVIEW from loading untrusted files
    Affected if No application control policies are configured, or LabVIEW can execute loaded VI scripts without restriction

If an affected LabVIEW version (2020 through 2024) is installed and users can open .vi files from any source without security restrictions, the environment is vulnerable to RCE via specially crafted VI files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 2020
Interim mitigation

Avoid opening VI files from untrusted or unverified sources. Apply vendor patches from National Instruments when released. Implement application whitelisting and endpoint protection to mitigate risks from malicious file execution.

Recommended fix Moderate confidence

LabVIEW 2024 Q2 or later

  1. 1. Download LabVIEW version 2024 Q2 or later from the official NI website (www.ni.com)
  2. 2. Uninstall the current vulnerable LabVIEW installation
  3. 3. Install the updated LabVIEW version
  4. 4. Ensure LabVIEW is updated to the latest Q2 release or subsequent releases
  5. 5. Educate users to only open VI files from trusted sources, as exploitation requires user interaction with a specially crafted VI file
Caveat Newer LabVIEW versions may have changes to VI compatibility and might require re-saving VIs in the new format; verify that any custom modules or toolkits are compatible with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Labview Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-23612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-23612 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data