Cyber Resilience

CVE-2024-10494

Memory Safety in Ni Labview ≤ 2021

Published
10 December 2024
Modified
04 March 2025
Patch / advisory
CVSS Score v4 8.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0019 9th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2024-10494 is a high-severity Improper Validation of Specified Index, Position, or Offset in Input (CWE-1285) vulnerability in Ni Labview. Its CVSS base score is 8.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 9th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An out of bounds read due to improper input validation in HeapObjMapImpl.cpp in NI LabVIEW may disclose information or result in arbitrary code execution. Successful exploitation requires an attacker to provide a user with a specially crafted VI. This vulnerability…

more

affects LabVIEW 2024 Q3 and prior versions.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-10496Same product: Ni Labview
CVE-2024-10495Same product: Ni Labview
CVE-2025-64465Same product: Ni Labview
CVE-2026-32863Same product: Ni Labview
CVE-2024-4079Same product: Ni Labview
CVE-2025-64464Same product: Ni Labview
CVE-2025-64462Same product: Ni Labview
CVE-2026-32864Same product: Ni Labview
CVE-2025-64463Same product: Ni Labview
CVE-2025-64466Same product: Ni Labview

Affected Assets

ni
labview
2022, 2023, 2024 · ≤ 2021

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.4.2
  • V2.1.1
  • V2.2.1
  • V2.2.2

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.

Requires explicit validation of supplied indices/offsets/positions before they are used to access buffers or other indexable resources.

Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.

Process isolation confines the effects of an out-of-bounds read to the compromised process.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation, preventing this class of flaw at development time.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover missing index validation via scanning or reviews.

PR.PS-02 partial match
prevents

Patching and replacement can remediate instances of the weakness after discovery.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect missing or incorrect index validation during development and acceptance.

A.8.15 Logging partial match
finds

Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.

prevents

Secure development lifecycle includes input validation requirements that can prevent improper index handling.

prevents

Application security requirements typically mandate bounds checking and validation of offsets/indices.

prevents

Secure architecture principles include defensive input validation and bounds checking for indexable resources.

prevents

Secure coding standards directly require validation of indices, positions, and offsets before use.

References