dbcve.org
Bentley ViewApplication · Bentley

CVE-2021-34931

HIGH · 7.8 CVSS v3.1 Published 2022-01-13
Fix available
A fix is available. Upgrade to 10.16.02 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
This 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 validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14909.

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 confidence

A NULL pointer dereference vulnerability in Bentley View 10.15.0.75 allows remote code execution via malicious JT files. The parser fails to validate object existence before performing operations on it, enabling an attacker to execute arbitrary code in the context of the current process when a user opens a specially crafted JT file.

MitigationApply the vendor patch from Bentley. Until then, avoid opening JT files from untrusted sources.

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
Bentley ViewApplication
Affected:< 10.16.02
MicrostationApplication
Affected:< 10.16.02

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. Check Bentley View version
    Locate the Bentley View installation and retrieve its version number (typically via Help > About, the application's executable properties, or the installed programs list)
    Affected if Version is below 10.16.02 (any version from 10.15.0.75 down to earlier versions)
  2. Check Microstation version
    Locate the Microstation installation and retrieve its version number (via Help > About, executable properties, or installed programs list)
    Affected if Version is below 10.16.02 (any version from 10.15.0.75 down to earlier versions)
  3. Verify JT file handling is enabled
    Check if the Bentley product has JT file parsing or viewing capabilities enabled (look for JT translator settings, file associations for .jt files, or JT import/export plugins)
    Affected if JT file handling capability exists in the installed product
  4. Inspect recent JT file activity
    Review recent documents, file open history, or application logs for evidence of .jt file processing
    Affected if Any .jt files have been opened in the affected product

User is affected if either Bentley View or Microstation is installed with a version lower than 10.16.02 and the product is capable of processing JT files.

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 10.16.02 or later
Fixed in 10.16.02
Interim mitigation

Apply the vendor patch from Bentley. Until then, avoid opening JT files from untrusted sources.

Recommended fix Moderate confidence

10.16.02 or later

  1. Check current Bentley View or MicroStation version via Help > About
  2. Navigate to the Bentley product download page or use the Bentley Softdesk license utility to obtain version 10.16.02 or later
  3. Download the installer for version 10.16.02 or newer
  4. Close all Bentley applications and any running JT file processes
  5. Run the installer and follow the prompts to upgrade the product
  6. Restart the application and verify the version shows 10.16.02 or later under Help > About
  7. Avoid opening untrusted JT files from unknown sources as a temporary mitigation until the upgrade is applied
Caveat Ensure any custom workspaces, standards, or configuration files are backed up before upgrading, as they may require revalidation against the new version

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

Fix this in Bentley View Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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