CVE-2024-23612 | Improper Error Handling Issue in LabVIEW

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.

Published: 2024-03-11 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-23612 is rated Moderate Risk (46.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.60%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-23612

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.39% 0.60% +0.21%
2 2025-11-21 0.20% 0.39% +0.19%
3 2025-11-18 — 0.20% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-23612

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2024-23612

Affected software / configurations for CVE-2024-23612

Vendor Product Version Raw CPE
ni labview <= 2020 cpe:2.3:a:ni:labview:*:*:*:*:*:*:*:*
ni labview 2021 cpe:2.3:a:ni:labview:2021:-:*:*:-:*:*:*
ni labview 2021 cpe:2.3:a:ni:labview:2021:sp1:*:*:*:*:*:*
ni labview 2022 cpe:2.3:a:ni:labview:2022:q1:*:*:*:*:*:*
ni labview 2022 cpe:2.3:a:ni:labview:2022:q3:*:*:*:*:*:*
ni labview 2023 cpe:2.3:a:ni:labview:2023:q1:*:*:*:*:*:*
ni labview 2023 cpe:2.3:a:ni:labview:2023:q3:*:*:*:*:*:*
ni labview 2023 cpe:2.3:a:ni:labview:2023:q3_patch1:*:*:*:*:*:*
ni labview 2023 cpe:2.3:a:ni:labview:2023:q3_patch2:*:*:*:*:*:*
ni labview 2024 cpe:2.3:a:ni:labview:2024:q1:*:*:*:*:*:*

References for CVE-2024-23612

cvelogic Threat Intelligence