dbcve.org
Jt2goApplication · Siemens

CVE-2023-28830

HIGH · 7.8 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 13.2.0.15 / 13.3.0.11 or later.
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 JT2Go (All versions < V14.2.0.5), Solid Edge SE2022 (All versions < V222.0 Update 13), Solid Edge SE2023 (All versions < V223.0 Update 4), Teamcenter Visualization V13.2 (All versions < V13.2.0.15), Teamcenter Visualization V13.3 (All versions < V13.3.0.11), Teamcenter Visualization V14.1 (All versions < V14.1.0.11), Teamcenter Visualization V14.2 (All versions < V14.2.0.5). The affected application contains a use-after-free vulnerability that could be triggered while parsing specially crafted ASM file. An attacker could leverage this vulnerability 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 confidence

A use-after-free vulnerability exists in JT2Go, Solid Edge SE2022/SE2023, and Teamcenter Visualization (multiple versions) when parsing specially crafted ASM files. The vulnerability allows an attacker to execute arbitrary code in the context of the current process by exploiting the freed memory access.

MitigationUpdate affected products to the vendor-specified patched versions: JT2Go to V14.2.0.5 or later, Solid Edge SE2022 to V222.0 Update 13 or later, Solid Edge SE2023 to V223.0 Update 4 or later, and Teamcenter Visualization to the corresponding version for each release branch (V13.2.0.15, V13.3.0.11, V14.1.0.11, or V14.2.0.5).

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
Jt2goApplication
Affected:< 14.2.0.5
Teamcenter VisualizationApplication
Affected:>= 13.2.0, < 13.2.0.15>= 13.3.0, < 13.3.0.11>= 14.1, < 14.1.0.11>= 14.2, < 14.2.0.5
Solid Edge Se2022Web browser
Affected:all versions= maintenance_pack_1= maintenance_pack_2= maintenance_pack_3= maintenance_pack_4= maintenance_pack_5= maintenance_pack_7= maintenance_pack_8= maintenance_pack_9= maintenance_pack_10= maintenance_pack_11= maintenance_pack_12
Solid Edge Se2023Web browser
Affected:all versions= update_0001= update_0002= update_0003

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. Identify installed Siemens product
    Check Programs and Features or the application Help > About section for one of: JT2Go, Solid Edge SE2022, Solid Edge SE2023, or Teamcenter Visualization
    Affected if Any of these products are installed
  2. Determine JT2Go version
    Open JT2Go, go to Help > About JT2Go and note the version number (e.g., 14.1.0.0)
    Affected if Version is lower than 14.2.0.5
  3. Determine Teamcenter Visualization version
    Open the application, check Help > About or right-click the executable > Properties > Details for the version field. Check all four release branches if multiple versions exist
    Affected if Version is 13.2.0.x below 13.2.0.15, OR 13.3.0.x below 13.3.0.11, OR 14.1.0.x below 14.1.0.11, OR 14.2.0.x below 14.2.0.5
  4. Determine Solid Edge SE2022 version
    Open Solid Edge SE2022, go to Help > About Solid Edge SE2022. Note the main version and any maintenance pack number displayed
    Affected if Any version of SE2022 is installed (all versions are affected per the advisory)
  5. Determine Solid Edge SE2023 version
    Open Solid Edge SE2023, go to Help > About Solid Edge SE2023. Note the main version and update number displayed
    Affected if Any version of SE2023 is installed (all versions are affected per the advisory)

The environment is affected if JT2Go is below 14.2.0.5, Teamcenter Visualization falls within any of the four vulnerable version ranges, or any Solid Edge SE2022/SE2023 installation exists, since the use-after-free triggers when parsing specially crafted ASM files.

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
Upgrade available Upgrade to 13.2.0.15 / 13.3.0.11 / 14.1.0.11 or later
Fixed in 13.2.0.1513.3.0.1114.1.0.11
Interim mitigation

Update affected products to the vendor-specified patched versions: JT2Go to V14.2.0.5 or later, Solid Edge SE2022 to V222.0 Update 13 or later, Solid Edge SE2023 to V223.0 Update 4 or later, and Teamcenter Visualization to the corresponding version for each release branch (V13.2.0.15, V13.3.0.11, V14.1.0.11, or V14.2.0.5).

Recommended fix High confidence

JT2Go: V14.2.0.5+ | Teamcenter Visualization V13.2: V13.2.0.15+ | Teamcenter Visualization V13.3: V13.3.0.11+ | Teamcenter Visualization V14.1: V14.1.0.11+ | Teamcenter Visualization V14.2: V14.2.0.5+ | Solid Edge SE2022: V222.0 Update 13+ | Solid Edge SE2023: V223.0 Update 4+

  1. Identify the current version of the affected Siemens product (JT2Go, Teamcenter Visualization, or Solid Edge)
  2. For JT2Go: upgrade to version 14.2.0.5 or later
  3. For Teamcenter Visualization V13.2: upgrade to version 13.2.0.15 or later
  4. For Teamcenter Visualization V13.3: upgrade to version 13.3.0.11 or later
  5. For Teamcenter Visualization V14.1: upgrade to version 14.1.0.11 or later
  6. For Teamcenter Visualization V14.2: upgrade to version 14.2.0.5 or later
  7. For Solid Edge SE2022: upgrade to V222.0 Update 13 or later
  8. For Solid Edge SE2023: upgrade to V223.0 Update 4 or later

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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