dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-12742

HIGH · 7.8 CVSS v3.1 Published 2025-03-06
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 G Web Development Software that may result in arbitrary code execution.  Successful exploitation requires an attacker to get a user to open a specially crafted project file.  This vulnerability affects G Web Development Software 2022 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 · high confidence

This is a deserialization vulnerability in NI G Web Development Software where specially crafted project files can contain malicious serialized data. When a user opens these files, the vulnerable deserialization process interprets the data in an unsafe manner, allowing arbitrary code execution on the victim's machine.

MitigationUpgrade NI G Web Development Software to a version newer than 2022 Q3. Until patched, exercise extreme caution with project files from untrusted sources and consider application whitelisting controls.

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 G Web Development Software is installed
    Check the system for the presence of NI G Web Development Software. This may be via Add/Remove Programs on Windows, a package manager on Linux, or by searching for NI G Web Development related executables or directories.
    Affected if The software is found on the system
  2. Determine the installed version
    Locate and read the version information for NI G Web Development Software. This is typically accessible through the software itself (Help > About), the Windows registry, or installation directories. If no version is displayed, check the original installer or release documentation for the installed build.
    Affected if The version cannot be determined or is older than the 2022 Q3 release
  3. Compare against affected version range
    Review the identified version against the known affected range. According to the provided information, versions older than 2022 Q3 are affected by this deserialization vulnerability.
    Affected if The installed version is older than 2022 Q3
  4. Assess project file handling exposure
    Determine if the software is used to open project files, particularly from untrusted sources. The vulnerability specifically involves malicious serialized data in project files that are processed during file opening.
    Affected if Users routinely open NI G Web Development project files, especially from external or untrusted sources

A system is affected if NI G Web Development Software is installed with a version older than 2022 Q3 and users open project files with the software.

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

Upgrade NI G Web Development Software to a version newer than 2022 Q3. Until patched, exercise extreme caution with project files from untrusted sources and consider application whitelisting controls.

Recommended fix Moderate confidence

G Web Development Software 2022 Q4 or later

  1. 1. Identify the current version of NI G Web Development Software installed by opening the software and checking Help > About or checking the installed programs list in Windows Control Panel.
  2. 2. Navigate to the NI (National Instruments) website or contact NI support to obtain the latest version of G Web Development Software.
  3. 3. Download and install a version of G Web Development Software released after 2022 Q3 (such as 2022 Q4 or later), as these versions contain the security fix for CVE-2024-12742.
  4. 4. After upgrading, verify the installation was successful by checking the software version again.
  5. 5. Ensure all project files are tested to confirm functionality is maintained after the upgrade.
Caveat Review NI release notes for the target version to check for any breaking changes or migration requirements from 2022 Q3

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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