CVE-2024-34086
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 · uneditedA vulnerability has been identified in JT2Go (All versions < V2312.0001), Teamcenter Visualization V14.1 (All versions < V14.1.0.13), Teamcenter Visualization V14.2 (All versions < V14.2.0.10), Teamcenter Visualization V14.3 (All versions < V14.3.0.7), Teamcenter Visualization V2312 (All versions < V2312.0001). The affected applications contain an out of bounds write vulnerability when parsing a specially crafted CGM file. This could allow an attacker to 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 confidenceAn out-of-bounds write vulnerability exists in the CGM file parsing code of JT2Go and Teamcenter Visualization applications. By supplying a specially crafted CGM file, an attacker can trigger a buffer overflow and execute arbitrary code in the context of the current process.
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< 2312.0001>= 14.1, < 14.1.0.13>= 14.2, < 14.2.0.10>= 14.3, < 14.3.0.7>= 2312.0, < 2312.0001CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check JT2Go versionLocate JT2Go installation directory and check the version information. On Windows, this can often be found in Add/Remove Programs, or right-click on the JT2Go executable and view Properties > Details for the File Version. Alternatively, launch JT2Go and navigate to Help > About to view version information.Affected if The installed version is lower than 2312.0001 (for example, 14.0.x, 14.1.x, etc.)
-
Check Teamcenter Visualization versionLocate the Teamcenter Visualization installation and check the version. This is typically found in the software's About or Help menu, or by checking the installed program's version property in Add/Remove Programs. The version is usually displayed as a four-part number (e.g., 14.1.0.5).Affected if The installed version falls within any of these ranges: >= 14.1.0.0 and < 14.1.0.13; >= 14.2.0.0 and < 14.2.0.10; >= 14.3.0.0 and < 14.3.0.7; or >= 2312.0.0 and < 2312.0001
-
Identify CGM file handling capabilityBoth JT2Go and Teamcenter Visualization include native support for CGM (Computer Graphics Metafile) file parsing as a core feature. This functionality is built into the application and does not require separate module activation. To determine if CGM files are processed, check if the software can open .cgm files or if CGM import options appear in the application's file open dialog or import settings.Affected if The software is installed with CGM file handling enabled (which is the default configuration), and an affected version of the software is detected in the previous steps
A user is affected if they have JT2Go version below 2312.0001 or Teamcenter Visualization in one of the affected version ranges, and the software's CGM parsing feature (enabled by default) can be used to open files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped14.1.0.1314.2.0.1014.3.0.7
Apply the vendor patches (JT2Go V2312.0001, Teamcenter Visualization V14.1.0.13, V14.2.0.10, V14.3.0.7, or V2312.0001) to address the vulnerability. Avoid opening untrusted CGM files from unknown sources until patches are applied.
JT2Go: V2312.0001 | Teamcenter Visualization V14.1: V14.1.0.13 | Teamcenter Visualization V14.2: V14.2.0.10 | Teamcenter Visualization V14.3: V14.3.0.7 | Teamcenter Visualization V2312: V2312.0001
- 1. Identify the currently installed product (JT2Go or Teamcenter Visualization) and its exact version
- 2. For JT2Go: Upgrade to version 2312.0001 or later
- 3. For Teamcenter Visualization V14.1: Upgrade to version 14.1.0.13 or later
- 4. For Teamcenter Visualization V14.2: Upgrade to version 14.2.0.10 or later
- 5. For Teamcenter Visualization V14.3: Upgrade to version 14.3.0.7 or later
- 6. For Teamcenter Visualization V2312: Upgrade to version 2312.0001 or later
- 7. Download the appropriate fixed version from Siemens official support portal (cert-portal.siemens.com or Siemens Support Portal)
- 8. Follow standard software upgrade procedures for the specific product
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,784.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-34086 in production — separate from our analysis above.
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.
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.
- 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