dbcve.org
Jt2goApplication · Siemens

CVE-2022-29030

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-20
Fix available
A fix is available. Upgrade to 13.3.0.3 / 14.0.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges Patch available

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 < V13.3.0.3), Teamcenter Visualization V13.3 (All versions < V13.3.0.3), Teamcenter Visualization V14.0 (All versions < V14.0.0.1). The Mono_Loader.dll library is vulnerable to integer overflow condition while parsing specially crafted TG4 files. An attacker could leverage this vulnerability to crash the application causing denial of service condition.

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

A detailed technical summary for this CVE is being prepared.

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:< 13.3.0.3
Teamcenter VisualizationApplication
Affected:>= 13.3, < 13.3.0.3>= 14.0, < 14.0.0.1

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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.3.0.3 / 14.0.0.1 or later
Fixed in 13.3.0.314.0.0.1
Vendor patch cert-portal.siemens.com →
Recommended fix High confidence

JT2Go: V13.3.0.3 | Teamcenter Visualization V13.3: V13.3.0.3 | Teamcenter Visualization V14.0: V14.0.0.1

  1. Obtain the fixed version of the affected software from Siemens: JT2Go V13.3.0.3 or later, Teamcenter Visualization V13.3 V13.3.0.3 or later, or Teamcenter Visualization V14.0 V14.0.0.1 or later
  2. Download the updated software from the official Siemens support portal or contact Siemens customer support
  3. Backup all critical data and configurations before performing the upgrade
  4. Uninstall the current version of JT2Go or Teamcenter Visualization
  5. Install the upgraded version (V13.3.0.3 or later for JT2Go/V13.3, or V14.0.0.1 or later for V14.0)
  6. Verify the installation was successful by checking the version number in the application
  7. Test that TG4 file parsing functionality works correctly with the updated version
Caveat Review Siemens release notes for any functionality changes between current and fixed versions before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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