dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-12741

HIGH · 7.8 CVSS v3.1 Published 2024-12-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
A deserialization of untrusted data vulnerability exists in NI DAQExpress that may result in remote code execution. Successful exploitation requires an attacker to get a user to open a specially crafted project file. This vulnerability affects DAQExpress 5.1 and prior versions.  Please note that DAQExpress is an EOL product and will not receive any updates.

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

A deserialization vulnerability in NI DAQExpress 5.1 and prior allows remote code execution when a user opens a specially crafted project file. The vulnerability stems from unsafe deserialization of untrusted data embedded in project files, enabling attackers to execute arbitrary code on the victim's machine.

MitigationSince DAQExpress is end-of-life and will not receive patches, organizations should immediately cease use of the product, implement strict file handling controls to block untrusted DAQExpress project files, and migrate to actively maintained alternatives.

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

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. Verify NI DAQExpress is installed
    Check the installed programs list in Windows Control Panel or use 'Get-ItemProperty' in PowerShell for the registry key HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* to find NI DAQExpress entries
    Affected if NI DAQExpress appears in the installed programs list
  2. Determine the installed DAQExpress version
    Run 'Get-ItemProperty' on the DAQExpress installation directory or check the program's properties/About dialog for the exact version number
    Affected if The version is 5.1 or any version prior to 5.1
  3. Locate DAQExpress project files on the system
    Search for file extensions typically used by DAQExpress projects (such as .daqmx, .daqconfig, or similar) using PowerShell: Get-ChildItem -Path $env:USERPROFILE,'C:\' -Recurse -Include *.daqmx,*.daqconfig -ErrorAction SilentlyContinue
    Affected if Any .daqmx or related project files exist on the system, especially in accessible locations like downloads or shared folders
  4. Verify the project file handling feature is enabled
    Open DAQExpress and confirm the ability to open or import project files; check if the deserialization handler for project files is active by examining the application's loaded modules or available import features
    Affected if The application can open or import project files and the file parsing functionality is operational

You are affected if NI DAQExpress version 5.1 or prior is installed and the application can open or deserialize project 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since DAQExpress is end-of-life and will not receive patches, organizations should immediately cease use of the product, implement strict file handling controls to block untrusted DAQExpress project files, and migrate to actively maintained alternatives.

Recommended fix High confidence
  1. This vulnerability has no remediation path. NI DAQExpress has reached End of Life (EOL) and NI has confirmed the product will not receive any updates.
  2. Migrate to an actively supported NI software solution such as NI-DAQmx with Measurement & Automation Explorer (MAX) or LabVIEW with NI-DAQmx driver.
  3. If migration is not immediately possible, implement user education to prevent opening untrusted project files and restrict file access to trusted sources only.
Caveat Product is End of Life with no available fixes; requires migration to actively supported NI software

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

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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