dbcve.org
Jt2goApplication · Siemens

CVE-2022-3160

HIGH · 7.8 CVSS v3.1 Published 2023-01-13
Fix available
A fix is available. Upgrade to 13.3.0.8 / 14.0.0.4 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 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 (Adobe PDF Library) where an out-of-bounds write occurs when parsing specially crafted PDF files. This memory corruption allows an attacker to achieve code execution in the context of the vulnerable application process.

MitigationApply vendor patches for APDFL.dll when available; until then, avoid opening untrusted or unsolicited PDF files, as the vulnerability is triggered during PDF parsing.

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.1.0.5
Teamcenter VisualizationApplication
Affected:>= 13.3.0, < 13.3.0.8>= 14.0, < 14.0.0.4>= 14.1, < 14.1.0.5

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 Jt2go version
    Locate the Jt2go installation directory and check the version information. Common paths include C:\Program Files\Siemens\Jt2go or C:\Program Files (x86)\Siemens\Jt2go. Right-click the main executable (Jt2go.exe) and select Properties > Details to view the File Version.
    Affected if The installed version is lower than 14.1.0.5
  2. Identify installed Siemens Teamcenter Visualization version
    Locate the Teamcenter Visualization installation and check the version. Common paths include C:\Program Files\Siemens\Teamcenter<version>\Visualization. Check the file version of the main visualization executable or the product information in the installation directory.
    Affected if The version matches any of these ranges: >=13.3.0 but <13.3.0.8, >=14.0 but <14.0.0.4, or >=14.1 but <14.1.0.5
  3. Locate and verify APDFL.dll version
    Search for APDFL.dll within the product installation directory. Common locations include the bin or lib subdirectory. Right-click the DLL file, select Properties > Details, and note the Product Version or File Version.
    Affected if APDFL.dll version is present and corresponds to an affected Adobe PDF Library version used by the vulnerable application
  4. Confirm PDF parsing functionality is in use
    Review whether the application has been used to open, preview, or process PDF files. The vulnerability triggers specifically during PDF file parsing when a specially crafted PDF is opened.
    Affected if Users have opened or previewed PDF documents using the affected application

You are affected if either Siemens Jt2go version is below 14.1.0.5 or Siemens Teamcenter Visualization version falls within any of the three affected ranges (13.3.0-13.3.0.7, 14.0-14.0.0.3, or 14.1-14.1.0.4) and the application has been used to parse PDF 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.3.0.8 / 14.0.0.4 / 14.1.0.5 or later
Fixed in 13.3.0.814.0.0.414.1.0.5
Interim mitigation

Apply vendor patches for APDFL.dll when available; until then, avoid opening untrusted or unsolicited PDF files, as the vulnerability is triggered during PDF parsing.

Recommended fix High confidence

Jt2go: 14.1.0.5 | Teamcenter Visualization: 13.3.0.8 or 14.0.0.4 or 14.1.0.5 (depending on current major version)

  1. Identify the affected product in use (Jt2go or Teamcenter Visualization)
  2. Determine the currently installed version number
  3. For Jt2go: Upgrade to version 14.1.0.5 or later
  4. For Teamcenter Visualization on version 13.3.x: Upgrade to version 13.3.0.8 or later
  5. For Teamcenter Visualization on version 14.0.x: Upgrade to version 14.0.0.4 or later
  6. For Teamcenter Visualization on version 14.1.x: Upgrade to version 14.1.0.5 or later
  7. Test the upgraded software to verify the vulnerability is remediated and functionality is intact
Caveat Major version upgrades may introduce compatibility changes; test in non-production environment first

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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