dbcve.org
Jt2goApplication · Siemens

CVE-2023-1709

HIGH · 7.8 CVSS v3.1 Published 2023-06-07
Fix available
A fix is available. Upgrade to 13.2.0.13 / 13.3.0.9 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
Datalogics Library APDFLThe v18.0.4PlusP1e and prior contains a stack-based buffer overflow due to documents containing corrupted fonts, which could allow an attack that causes an unhandled crash during the rendering 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

The Datalogics APDFL library versions 18.0.4PlusP1e and prior contain a stack-based buffer overflow vulnerability when processing PDF documents with corrupted fonts, leading to memory corruption and an unhandled crash during the rendering process.

MitigationUsers should avoid opening untrusted PDF documents from unknown sources and ensure the library is updated to a patched version once available from the vendor.

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.2
Teamcenter VisualizationApplication
Affected:>= 13.2.0, < 13.2.0.13>= 13.3.0, < 13.3.0.9>= 14.0, < 14.0.0.5>= 14.1, < 14.1.0.7>= 14.2, < 14.2.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 Siemens Jt2go or Teamcenter Visualization installation by inspecting Program Files directory or Windows registry under HKLM\SOFTWARE\Siemens or HKLM\SOFTWARE\WOW6432Node\Siemens
    Affected if Either Jt2go or Teamcenter Visualization is present on the system
  2. Determine Jt2go version
    Locate Jt2go executable (typically in C:\Program Files\Siemens\JT2Go or C:\Program Files (x86)\Siemens\JT2Go) and check file properties for version, or query registry key HKLM\SOFTWARE\Siemens\JT2Go\ProductVersion
    Affected if Version is present and less than 14.2.0.2
  3. Determine Teamcenter Visualization version
    Locate Teamcenter Visualization executable and check file properties for version, or query registry under HKLM\SOFTWARE\Siemens\Teamcenter\Visualization for the installed version string
    Affected if Version falls within any of these ranges: >= 13.2.0 and < 13.2.0.13; >= 13.3.0 and < 13.3.0.9; >= 14.0 and < 14.0.0.5; >= 14.1 and < 14.1.0.7; or >= 14.2 and < 14.2.0.2
  4. Locate APDFL library file
    Search for apdfl*.dll or Datalogics related DLL files within the Siemens product installation directory, typically found in the bin or lib subfolder
    Affected if The Datalogics APDFL library (versions 18.0.4PlusP1e or prior) is present in the product installation folder

The environment is affected if Siemens Jt2go version is below 14.2.0.2, or Siemens Teamcenter Visualization version falls within any of the specified vulnerable ranges, and the Datalogics APDFL library is used for PDF processing.

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.13 / 13.3.0.9 / 14.0.0.5 or later
Fixed in 13.2.0.1313.3.0.914.0.0.5
Interim mitigation

Users should avoid opening untrusted PDF documents from unknown sources and ensure the library is updated to a patched version once available from the vendor.

Recommended fix High confidence

Jt2go >= 14.2.0.2; Teamcenter Visualization >= 13.2.0.13 (13.2.x), >= 13.3.0.9 (13.3.x), >= 14.0.0.5 (14.0.x), >= 14.1.0.7 (14.1.x)

  1. For Jt2go: Upgrade to version 14.2.0.2 or later
  2. For Teamcenter Visualization (13.2.0.x branch): Upgrade to version 13.2.0.13 or later
  3. For Teamcenter Visualization (13.3.0.x branch): Upgrade to version 13.3.0.9 or later
  4. For Teamcenter Visualization (14.0.x branch): Upgrade to version 14.0.0.5 or later
  5. For Teamcenter Visualization (14.1.x branch): Upgrade to version 14.1.0.7 or later

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

Fix this in Jt2go Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
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,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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