CVE-2021-34934
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 · uneditedThis vulnerability allows remote attackers to execute arbitrary code on affected installations of Bentley View 10.15.0.75. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of JT files. The issue results from the lack of proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14912.
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 confidenceMemory corruption vulnerability in Bentley View 10.15.0.75 during JT file parsing due to lack of proper validation of user-supplied data. Attack requires user to open a malicious JT file, allowing arbitrary code execution 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< 10.16.02< 10.16.02CVSS 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 Bentley productCheck for Bentley View or Microstation installation by searching Program Files for 'Bentley' folder, or check registry under HKEY_LOCAL_MACHINE\SOFTWARE\Bentley SystemsAffected if Neither Bentley View nor Microstation is installed, then not affected
-
Determine installed version of Bentley ViewRight-click the Bentley View executable, select Properties, then look at the Details tab for Product Version. If not found, open Bentley View and go to Help > About Bentley ViewAffected if Version is less than 10.16.02 (e.g., 10.15.0.75 or any 10.x version below 10.16.02)
-
Determine installed version of MicrostationOpen Microstation and go to Help > About Microstation, or right-click the executable in Program Files and check Properties > Details for Product VersionAffected if Version is less than 10.16.02 (any version below 10.16.02)
-
Verify JT file parsing capability is presentOpen Bentley View or Microstation and attempt to open a .jt file, or check if the application has JT translator/loader modules loaded. The vulnerability triggers when processing JT filesAffected if The application can open or process JT files and the version is below 10.16.02
User is affected if either Bentley View or Microstation is installed with a version lower than 10.16.02 and the application has the ability to parse JT 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.
dbcve · scoped10.16.02
Update Bentley View to the vendor's patched version. Avoid opening JT files from untrusted sources.
Bentley View 10.16.02 or later / Microstation 10.16.02 or later
- Identify whether Bentley View or Microstation is in use
- Check the current installed version (must be less than 10.16.02)
- Download version 10.16.02 or later from the official Bentley website (www.bentley.com)
- Install the update following Bentley's standard upgrade procedure
- Verify the installed version is 10.16.02 or higher after update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34934 — 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-34934 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