CVE-2021-34326
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 · uneditedA vulnerability has been identified in JT2Go (All versions < V13.2), Solid Edge SE2021 (All Versions < SE2021MP5), Teamcenter Visualization (All versions < V13.2). The plmxmlAdapterSE70.dll library in affected applications lacks proper validation of user-supplied data when parsing PAR files. This could result in an out of bounds write past the fixed-length heap-based buffer. An attacker could leverage this vulnerability to execute code in the context of the current process. (ZDI-CAN-13422)
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 confidenceThe plmxmlAdapterSE70.dll library in JT2Go, Solid Edge SE2021, and Teamcenter Visualization lacks proper validation of user-supplied data when parsing PAR files. This insufficient validation leads to an out-of-bounds write past a fixed-length heap-based buffer. An attacker could exploit this to execute arbitrary code in the context of the current process.
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< se2021= se2021< 13.2.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 installed Siemens productCheck if JT2Go, Solid Edge SE2021, or Teamcenter Visualization is installed by reviewing installed programs or the product executable locations (typically in Program Files/Siemens)Affected if Any of these three products are installed on the system
-
Determine JT2Go versionIf JT2Go is installed, locate the executable (typically JT2Go.exe) and check its version properties, or look in the application help/about sectionAffected if Version is below 13.2.0 (e.g., 13.1.x or earlier)
-
Determine Solid Edge SE2021 versionIf Solid Edge is installed, check the version from the executable or in Add/Remove Programs; look for SE2021 with any patch level below MP5Affected if Version is se2021 (any build) or se2021 without MP5 patch applied
-
Determine Teamcenter Visualization versionIf Teamcenter Visualization is installed, check the version from the installed program or executable propertiesAffected if Version is below 13.2.0 (e.g., 13.1.x or earlier)
-
Verify plmxmlAdapterSE70.dll presenceSearch for plmxmlAdapterSE70.dll in the product installation directory (typically under Siemens folder in Program Files)Affected if The vulnerable DLL exists in the product installation folder
The environment is affected if JT2Go version <13.2.0, Solid Edge SE2021 without MP5, or Teamcenter Visualization version <13.2.0 is installed, and the plmxmlAdapterSE70.dll library is present for parsing PAR files.
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.
From vendor data13.2.0
Apply vendor patches: upgrade JT2Go and Teamcenter Visualization to version V13.2 or later, and Solid Edge SE2021 to version SE2021MP5 or later.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34326 — 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-34326 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