CVE-2021-38405
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 · uneditedThe Datalogics APDFL library used in affected products is vulnerable to memory corruption condition while parsing specially crafted PDF files. An attacker could leverage this vulnerability 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 confidenceA memory corruption vulnerability exists in the Datalogics APDFL library when parsing specially crafted PDF files. The vulnerability allows an attacker to achieve arbitrary code execution within the context of the current process by exploiting the memory corruption condition.
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< 13.2.0.7>= 13.1.0, < 13.1.0.8>= 13.2.0, < 13.2.0.7= 13.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Siemens Jt2go is installedCheck the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Siemens Jt2go' or locate the executable jt2go.exe in the installation directory (typically C:\Program Files\Siemens\Jt2go)Affected if The product is installed and the version is below 13.2.0.7
-
Identify if Siemens Teamcenter Visualization is installedCheck the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'Siemens Teamcenter Visualization' or locate the visualization executable in the installation directoryAffected if The product is installed and the version falls within 13.1.0 through 13.1.0.7, 13.2.0 through 13.2.0.6, or exactly 13.3.0
-
Determine the exact version of Jt2goRun 'jt2go.exe -version' from the installation directory or right-click the executable, select Properties, and check the File Version in the Details tabAffected if The version shown is less than 13.2.0.7
-
Determine the exact version of Teamcenter VisualizationRun the visualization component with a version flag or right-click the main executable, select Properties, and check the File Version in the Details tabAffected if The version is 13.1.0.x (where x is 0-7), 13.2.0.x (where x is 0-6), or exactly 13.3.0
-
Confirm PDF processing is in useReview application logs or user workflows to determine if the product is being used to open, view, or parse PDF documents, as exploitation requires processing a specially crafted PDF fileAffected if PDF files are being processed by the affected software version
A user is affected if they have Siemens Jt2go version below 13.2.0.7 or Siemens Teamcenter Visualization version 13.1.0.x (x < 8), 13.2.0.x (x < 7), or 13.3.0, and are processing PDF files with that software.
Generated from the published advisory. Verify against your own configuration.
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 · scoped13.1.0.813.2.0.7
Update the Datalogics APDFL library to the latest patched version. Until patches are available, implement input validation and sandboxing around PDF processing operations.
Jt2go: 13.2.0.7 or later; Teamcenter Visualization: 13.1.0.8, 13.2.0.7, or a later version
- 1. Identify the installed version of Jt2go or Teamcenter Visualization in your environment
- 2. For Jt2go: If version is below 13.2.0.7, plan upgrade to version 13.2.0.7 or later
- 3. For Teamcenter Visualization: If version is 13.1.0.x (where x < 8), upgrade to 13.1.0.8 or later
- 4. For Teamcenter Visualization: If version is 13.2.0.x (where x < 7), upgrade to 13.2.0.7 or later
- 5. For Teamcenter Visualization: If version is 13.3.0, upgrade to 13.2.0.7 (or a later fixed version) or apply any available patch for 13.3.0
- 6. Obtain the update from the official Siemens support portal or through your existing support agreement
- 7. Test the update in a non-production environment before deploying to production
- 8. Apply the update following standard change management procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38405 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-38405 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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