Stack-based Buffer OverflowWeakness · CWE-121

CVE-2024-37997

HIGH · 7.8 CVSS v3.1 Published 2024-07-09

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

NVD · unedited

A vulnerability has been identified in JT Open (All versions < V11.5), JT2Go (All versions < V2406.0003), PLM XML SDK (All versions < V7.1.0.014), Teamcenter Visualization V14.2 (All versions < V14.2.0.13), Teamcenter Visualization V14.3 (All versions < V14.3.0.11), Teamcenter Visualization V2312 (All versions < V2312.0008), Teamcenter Visualization V2406 (All versions < V2406.0003). The affected applications contain a stack based overflow vulnerability while parsing specially crafted XML files. This could allow an attacker to execute code in the context of the current process.

Technical summary

dbcve analysis · high confidence

Stack-based buffer overflow vulnerability in XML parsing across multiple Siemens PLM products (JT Open, JT2Go, PLM XML SDK, Teamcenter Visualization). Attackers can achieve remote code execution by tricking users into opening specially crafted malicious XML files, which overflow the stack buffer during parsing.

MitigationUpdate affected applications to vendor-supplied fixed versions: JT Open V11.5+, JT2Go V2406.0003+, PLM XML SDK V7.1.0.014+, Teamcenter Visualization V14.2.0.13+, V14.3.0.11+, V2312.0008+, V2406.0003+. Until patched, avoid opening untrusted XML files from unknown sources.

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

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify installed Siemens PLM product

Check the Windows Start Menu or program files directory for JT Open, JT2Go, PLM XML SDK, or Teamcenter Visualization. Open the application and navigate to Help > About to see the product name.

Affected if Any of these four Siemens PLM products is installed on the system
Determine JT Open version

Locate the JT Open installation directory. Right-click on the JT Open executable or DLL file, select Properties, and check the Details tab for the version number. Alternatively, open JT Open and go to Help > About JT Open.

Affected if The installed version is earlier than V11.5
Determine JT2Go version

Open JT2Go and navigate to Help > About JT2Go. The version number is displayed in the dialog. Alternatively, check the file properties of the JT2Go executable in the installation folder.

Affected if The installed version is earlier than V2406.0003
Determine PLM XML SDK version

Check the installed SDK documentation or manifest file, or query the SDK DLL version property in the installation directory. Look for a version file or assembly info.

Affected if The installed version is earlier than V7.1.0.014
Determine Teamcenter Visualization version

Open Teamcenter Visualization application and go to Help > About Teamcenter. The version information is displayed in the About dialog box.

Affected if The installed version is earlier than V14.2.0.13, V14.3.0.11, V2312.0008, or V2406.0003 depending on the release line

The user is affected if any of the four Siemens PLM products (JT Open, JT2Go, PLM XML SDK, or Teamcenter Visualization) is installed at a version below the corresponding fixed version thresholds listed in the detection steps.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Update affected applications to vendor-supplied fixed versions: JT Open V11.5+, JT2Go V2406.0003+, PLM XML SDK V7.1.0.014+, Teamcenter Visualization V14.2.0.13+, V14.3.0.11+, V2312.0008+, V2406.0003+. Until patched, avoid opening untrusted XML files from unknown sources.

Recommended fix High confidence

JT Open V11.5, JT2Go V2406.0003, PLM XML SDK V7.1.0.014, Teamcenter Visualization V14.2 V14.2.0.13, V14.3 V14.3.0.11, V2312 V2312.0008, V2406 V2406.0003

1. Identify the specific Siemens product in use from: JT Open, JT2Go, PLM XML SDK, or Teamcenter Visualization (versions V14.2, V14.3, V2312, or V2406)
2. Determine the current installed version of the product
3. Download the corresponding fixed version from official Siemens sources (cert-portal.siemens.com): JT Open V11.5 or later, JT2Go V2406.0003 or later, PLM XML SDK V7.1.0.014 or later, Teamcenter Visualization V14.2 V14.2.0.13 or later, V14.3 V14.3.0.11 or later, V2312 V2312.0008 or later, V2406 V2406.0003 or later
4. Back up all critical data before upgrading
5. Install the fixed version following Siemens installation documentation
6. Verify the installation was successful
7. Test that XML file parsing functionality works correctly

Caveat Review Siemens release notes for the specific version for any compatibility or migration considerations

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

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing6.0 h
Review / QA2.0 h

15.0 hours of engineering $2,580

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37997 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-37997?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

A high-priority fix

Have this fixed 15 hrs · Low

Typical engagement from $2,580

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-37997 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References