dbcve.org
Bentley ViewApplication · Bentley

CVE-2021-34940

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. Crafted data in a JT file can trigger a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15039.

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

Buffer overflow vulnerability in Bentley View's JT file parser. Crafted JT files containing malicious data can trigger a write operation past the end of an allocated buffer, allowing an attacker to execute arbitrary code in the context of the current user process.

MitigationApply the vendor-provided security patch for Bentley View. Until patched, users should not open 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. Confirm Bentley View or Microstation installation
    Check installed programs list in Windows Control Panel or use command: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Bentley*' -or $_.DisplayName -like '*Microstation*'}
    Affected if Either Bentley View or Microstation appears in installed programs
  2. Locate the installed executable version
    Navigate to the product installation directory (typically C:\Program Files\Bentley\View or C:\Program Files\Bentley\MicroStation) and locate the main executable, then right-click > Properties > Details to view the File Version
    Affected if Executable is found in the expected Bentley installation path
  3. Extract the exact product version number
    Open the application, click Help > About Bentley View or About MicroStation to display the exact version (format typically shows as major.minor.build such as 10.16.00.x)
    Affected if Version displayed in the About dialog is readable
  4. Compare version against affected range
    Take the version number from step 3 and compare it numerically to 10.16.02 - for example, 10.16.00 or 10.15.x would be less than 10.16.02
    Affected if Installed version is less than 10.16.02 (for example, 10.16.00, 10.15.00, or any 10.x version below 10.16.02)

A user is affected if Bentley View or Microstation is installed with any version lower than 10.16.02, as the buffer overflow in the JT file parser only applies to unpatched versions in that range.

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-provided security patch for Bentley View. Until patched, users should not open JT files from untrusted sources.

Recommended fix High confidence

Bentley View / MicroStation 10.16.02

  1. Obtain Bentley View or MicroStation version 10.16.02 or later from the official Bentley website (www.bentley.com)
  2. Ensure all users close any running instances of Bentley View or MicroStation
  3. Back up any critical project files before proceeding with the update
  4. Install version 10.16.02 following Bentley's standard installation procedures
  5. Verify the installation completed successfully and the software launches without errors

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

Fix this in Bentley View Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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