dbcve.org
Jt2goApplication · Siemens

CVE-2022-3161

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 a memory corruption vulnerability 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 · moderate confidence

APDFL.dll (Adobe PDF Library) contains a memory corruption vulnerability that triggers when parsing specially crafted PDF files. The vulnerability allows an attacker to achieve code execution within the context of the current process, likely through a heap-based buffer overflow or similar memory safety flaw in PDF object parsing.

MitigationOrganizations should avoid opening untrusted or unverified PDF files and ensure all software using APDFL.dll is updated to the vendor's latest patched version. Deploying the patch across affected systems is the primary remediation pathway.

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 if Siemens Jt2go is installed
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Siemens Jt2go' or look for the application in Program Files (typically C:\Program Files\Siemens\Jt2go). Use 'Get-ItemProperty' or inspect the program's directory directly.
    Affected if The software is installed and its version is below 14.1.0.5
  2. Identify if Siemens Teamcenter Visualization is installed
    Check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Siemens Teamcenter Visualization' or look in Program Files for a Teamcenter Visualization directory. Use registry queries or directory inspection.
    Affected if The software is installed and its version falls within any of these ranges: 13.3.0 to 13.3.0.7, 14.0.0.0 to 14.0.0.3, or 14.1.0.0 to 14.1.0.4
  3. Locate the APDFL.dll file
    Search for APDFL.dll within the installation directories of the identified Siemens products. Common paths include the main application folder or subdirectories like 'bin' or 'lib'. Use Get-ChildItem or a file search tool.
    Affected if APDFL.dll is present in the Siemens software installation directory, indicating the vulnerable component is in use.
  4. Check the version of APDFL.dll
    Right-click the APDFL.dll file, select Properties, and examine the 'File version' or 'Product version' field on the Details tab. Alternatively, use PowerShell: (Get-Item 'path\to\APDFL.dll').VersionInfo.
    Affected if The APDFL.dll version is present and matches a version known to be distributed with the affected Siemens product versions listed above.

A system is affected if either Siemens Jt2go below version 14.1.0.5 or Siemens Teamcenter Visualization within any of the affected version ranges is installed, and the APDFL.dll component is 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.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

Organizations should avoid opening untrusted or unverified PDF files and ensure all software using APDFL.dll is updated to the vendor's latest patched version. Deploying the patch across affected systems is the primary remediation pathway.

Recommended fix High confidence

Jt2go: 14.1.0.5+ | Teamcenter Visualization: 13.3.0.8+ / 14.0.0.4+ / 14.1.0.5+

  1. 1. Identify the product in use (Jt2go or Teamcenter Visualization)
  2. 2. Determine the current installed version of the software
  3. 3. For Jt2go: Upgrade to version 14.1.0.5 or later
  4. 4. For Teamcenter Visualization: Determine the current major version (13.3.x, 14.0.x, or 14.1.x)
  5. 5. If on 13.3.x: Upgrade to 13.3.0.8 or later
  6. 6. If on 14.0.x: Upgrade to 14.0.0.4 or later
  7. 7. If on 14.1.x: Upgrade to 14.1.0.5 or later
  8. 8. Verify the upgrade was successful by checking the version number

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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