dbcve.org
Jt2goApplication · Siemens

CVE-2022-2069

HIGH · 7.8 CVSS v3.1 Published 2022-10-20
Fix available
A fix is available. Upgrade to 13.3.0.5 / 14.0.0.2 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
The APDFL.dll in Siemens JT2Go prior to V13.3.0.5 and Siemens Teamcenter Visualization prior to V14.0.0.2 contains an out of bounds write past the fixed-length heap-based buffer while parsing specially crafted PDF files. 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 confidence

A heap-based buffer overflow vulnerability exists in APDFL.dll when parsing PDF files in Siemens JT2Go and Teamcenter Visualization. The vulnerability allows an out-of-bounds write past a fixed-length heap buffer, enabling arbitrary code execution in the context of the current process.

MitigationUpdate Siemens JT2Go to version V13.3.0.5 or later and Siemens Teamcenter Visualization to version V14.0.0.2 or later to obtain the vendor patch.

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:< 13.3.0.5
Teamcenter VisualizationApplication
Affected:>= 13.3.0, < 13.3.0.5>= 14.0, < 14.0.0.2

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 for presence of Siemens JT2Go or Teamcenter Visualization in Programs and Features (Windows) or by locating the application executable
    Affected if Neither product is installed - not affected; either product is installed - continue to version check
  2. Determine JT2Go version
    Right-click JT2Go.exe, select Properties, check Product Version in Details tab, or run 'wmic product where "name like '%JT2Go%'" get version'
    Affected if Version is present and less than 13.3.0.5 - vulnerable
  3. Determine Teamcenter Visualization version
    Right-click Teamcenter Visualization executable, select Properties, check Product Version in Details tab, or run 'wmic product where "name like '%Teamcenter%'" get version'
    Affected if Version is >= 13.3.0.0 and < 13.3.0.5, OR >= 14.0.0.0 and < 14.0.0.2 - vulnerable
  4. Locate APDFL.dll component
    Search for APDFL.dll in the application installation directory (commonly in the bin or program folder of the Siemens product)
    Affected if APDFL.dll exists in the product directory - vulnerable component present (version check above determines exploitability)

User is affected if either Siemens JT2Go version < 13.3.0.5 or Siemens Teamcenter Visualization version 13.3.0.x (before 13.3.0.5) or 14.0.x (before 14.0.0.2) is installed, with APDFL.dll present in the application directory.

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.3.0.5 / 14.0.0.2 or later
Fixed in 13.3.0.514.0.0.2
Interim mitigation

Update Siemens JT2Go to version V13.3.0.5 or later and Siemens Teamcenter Visualization to version V14.0.0.2 or later to obtain the vendor patch.

Recommended fix High confidence

Jt2Go: 13.3.0.5 or later; Teamcenter Visualization: 14.0.0.2 or later (13.3.0.5 for 13.x branch)

  1. 1. Identify the installed Siemens product (Jt2Go or Teamcenter Visualization) and current version
  2. 2. For Jt2Go: upgrade to version 13.3.0.5 or later
  3. 3. For Teamcenter Visualization: if using version 13.x, upgrade to 13.3.0.5 or later; if using version 14.x, upgrade to 14.0.0.2 or later
  4. 4. Obtain the updated installer from Siemens official support portal (support.industry.siemens.com) or your Siemens account
  5. 5. Install the updated version following standard Siemens installation procedures
  6. 6. Verify the installed version matches the fixed release

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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