dbcve.org
LabviewApplication · Ni

CVE-2024-10496

HIGH · 7.8 CVSS v3.1 Published 2024-12-10
Fix available
A fix is available. Upgrade to after 2021 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 out of bounds read due to improper input validation in BuildFontMap in fontmgr.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 affects LabVIEW 2024 Q3 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 · moderate confidence

An out-of-bounds read vulnerability exists in the BuildFontMap function within fontmgr.cpp of NI LabVIEW due to improper input validation. Attackers can exploit this by providing users with specially crafted VI files, potentially allowing disclosure of sensitive information from memory or execution of arbitrary code.

MitigationOrganizations should instruct users to avoid opening VI files from untrusted or unknown sources and should apply the vendor patch (LabVIEW version beyond 2024 Q3) when released by NI.

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:<= 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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
    Open LabVIEW and go to Help > About LabVIEW, or check the version from the installer/media used. On Windows, also check Add/Remove Programs for National Software LabVIEW entries.
    Affected if The version shown is 2021 or earlier, 2022, 2023, or 2024 (any version within the affected ranges listed)
  2. Confirm LabVIEW installation directory exists
    Locate the LabVIEW executable (labview.exe) - typically in C:\Program Files\National Instruments\LabVIEW 20XX on Windows or /Applications/LabVIEW 20XX on macOS.
    Affected if LabVIEW is installed on the system at any version within the affected ranges
  3. Verify fontmgr.cpp component is present
    The vulnerable BuildFontMap function resides in the LabVIEW font management libraries bundled with the installation. These libraries are part of the core LabVIEW runtime and load automatically when LabVIEW starts or opens a VI file.
    Affected if LabVIEW is installed at an affected version - the vulnerable code is present in the core executable components used for VI file parsing

A system is affected if NI LabVIEW version 2021 or earlier, 2022, 2023, or 2024 is installed, since the vulnerable BuildFontMap function in fontmgr.cpp is included in these versions and automatically invoked when processing 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 2021
Interim mitigation

Organizations should instruct users to avoid opening VI files from untrusted or unknown sources and should apply the vendor patch (LabVIEW version beyond 2024 Q3) when released by NI.

Recommended fix High confidence

LabVIEW 2024 Q4 or later

  1. 1. Identify the current LabVIEW version installed by opening LabVIEW and navigating to Help > About LabVIEW
  2. 2. Download LabVIEW 2024 Q4 or later from www.ni.com or the NI Software Portal
  3. 3. Before upgrading, back up any custom VIs and projects
  4. 4. Run the installer for the new LabVIEW version
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. After installation, verify the LabVIEW version by checking Help > About LabVIEW (should show version 2024 Q4 or later)
  7. 7. Test that existing VIs open correctly in the new version
Caveat Minor: Some older VIs created in very old LabVIEW versions may require recalibration or re-serialization after major version upgrades; always test critical VIs before production deployment

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

Fix this in Labview Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-10496 — 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-10496 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