CVE-2023-51439 is an out of bounds read in Siemens JT2Go and Teamcenter Visualization, rated High (7.8). Opening a specially crafted CGM file could allow code execution in the context of the process. Update JT2Go to V14.3.0.6 or later and Teamcenter Visualization to the fixed release for your line.
What's affected
Siemens advisory SSA-794653 lists these affected versions and fixes:
| Product | Affected | Fixed |
|---|---|---|
| JT2Go | all versions before V14.3.0.6 | V14.3.0.6 or later |
| Teamcenter Visualization V13.3 | before V13.3.0.13 | V13.3.0.13 or later |
| Teamcenter Visualization V14.1 | before V14.1.0.12 | V14.1.0.12 or later |
| Teamcenter Visualization V14.2 | before V14.2.0.9 | V14.2.0.9 or later |
| Teamcenter Visualization V14.3 | before V14.3.0.6 | V14.3.0.6 or later |
The same advisory covers other CGM parsing issues with different CVE numbers. This post covers only CVE-2023-51439. The record gives CVSS 7.8 (High), vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, and the advisory agrees. The record's CISA KEV flag is false.
How to check if you're exposed
Open the application's About dialog on a sample of workstations and read the version. For a quick fleet check on Windows, list installed programs and look for JT2Go and Teamcenter Visualization:
Get-Package | Where-Object { $_.Name -match "JT2Go|Teamcenter Visualization" } | Select-Object Name, Version
Compare each version with the table above, using the row for your product line. Engineering teams often keep several Teamcenter Visualization lines side by side, so check every branch, not only the newest. Also check shared drives and viewers installed on laptops used by suppliers or contractors who exchange CGM or JT files with you.
What to do now
- Update JT2Go to V14.3.0.6 or later, and Teamcenter Visualization to the fixed version for your line from the table.
- Until you can update, follow Siemens' workaround and do not open untrusted CGM files in JT2Go or Teamcenter Visualization.
- Tell engineering and supplier contacts about the file source rule, since the trigger is a file that a person opens.
- Where you can, block CGM attachments from untrusted senders at the mail gateway.
- Apply Siemens' general security recommendations for protecting network access to the systems that run these viewers.
Why it matters
The record lists CWE-125 (Out-of-bounds Read). The advisory says the application reads past the end of an allocated structure while parsing specially crafted CGM files. File format parsers are a common home for this class of bug because they trust length and offset fields inside the file, and the file is attacker controlled.
The vector shows a local attack with user interaction, so the realistic route is persuading someone to open a file. Impact is rated high on all three axes because the advisory says code could run in the context of the current process. Treat engineering viewers as exposed to files from outside the company, and treat file handling rules as part of the control.
Quick check
Can this be triggered without anyone opening a file?
The advisory says the issue is triggered when the application reads a malicious CGM file, and the vector marks user interaction as required. Someone has to open the file.
How do I know which version is fixed?
Use the fixed version for your product line in the table above: V14.3.0.6 for JT2Go and V14.3, V14.2.0.9, V14.1.0.12 or V13.3.0.13 for the Teamcenter Visualization lines.
Sources
- Siemens advisory SSA-794653 (fetched, HTML version of the PDF cited in the record)
- Gold page for CVE-2023-51439
Last reviewed: 19 October 2026.
