dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2024-41908

HIGH · 7.8 CVSS v3.1 Published 2024-08-13
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 vulnerability has been identified in NX (All versions < V2406.3000). The affected applications contains an out of bounds read vulnerability while parsing specially crafted PRT files. This could allow an attacker to crash the application or execute code in the context of the current process.

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

NX (Siemens PLM software) contains an out-of-bounds read vulnerability when parsing specially crafted PRT part files. An attacker can trigger this by providing a malicious PRT file, potentially causing a denial of service (application crash) or achieving arbitrary code execution in the context of the running NX process.

MitigationUpgrade NX to version V2406.3000 or later. Until patched, avoid opening untrusted PRT files from unknown or untrusted sources.

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. Confirm NX installation
    Check for NX installation by searching for 'nx.exe' in common installation paths (e.g., C:\Program Files\Siemens\NX<version>\NXBIN\nx.exe) or by querying the Windows Registry under HKLM\SOFTWARE\Siemens\NX and HKLM\SOFTWARE\WOW6432Node\Siemens\NX for the installed product.
    Affected if NX software is found on the system.
  2. Identify installed NX version
    Read the Version value from the registry key found in the previous step (e.g., HKLM\SOFTWARE\Siemens\NX\<InstallDir>\Version) or right-click the nx.exe executable, select Properties, and view the File Version details.
    Affected if A version number is retrieved.
  3. Compare version to fixed release
    Compare the identified version string to the fixed release V2406.3000 using numeric comparison on the version components (V2406.3000 means 2406.3000 or higher).
    Affected if The installed version is lower than V2406.3000 (e.g., V2403, V2306, V12, etc.).
  4. Verify PRT file handling is possible
    Check if the NX installation includes the part file handling components by confirming the presence of the 'partfile' or 'prt' file association or examining the NX\UGII\partfiles directory.
    Affected if PRT file handling capability exists in the NX installation.
  5. Assess exposure to untrusted PRT files
    Review recent file access logs, examine NX workspace directories for recently opened PRT files, or check with users if they open PRT files from external or untrusted sources.
    Affected if Users process PRT files from unknown or untrusted sources with an affected NX version.

A system is affected if NX software is installed with a version lower than V2406.3000 and users can be tricked into opening a malicious PRT file.

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 NX to version V2406.3000 or later. Until patched, avoid opening untrusted PRT files from unknown or untrusted sources.

Recommended fix High confidence

V2406.3000

  1. 1. Ensure all users close any open NX sessions
  2. 2. Back up all critical NX part files (PRT) before proceeding
  3. 3. Obtain the fixed release V2406.3000 or later from Siemens
  4. 4. Run the installer for V2406.3000 on each affected workstation
  5. 5. Verify the installed version by checking NX Help > About Siemens NX (should show V2406.3000 or later)
  6. 6. Test that PRT file parsing works normally with the updated version
Caveat Review Siemens NX V2406.3000 release notes for any changes to file formats, APIs, or deprecated features that may affect existing workflows

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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