dbcve.org
Bentley ViewApplication · Bentley

CVE-2021-34876

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-14828.

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 buffer overflow vulnerability exists in Bentley View 10.15.0.75 during JT file parsing. When processing a maliciously crafted JT file, the parser writes data past the end of an allocated buffer, allowing an attacker to execute arbitrary code in the context of the current process. User interaction is required (opening a malicious file).

MitigationUsers should avoid opening JT files from untrusted sources. Apply vendor patches when released by Bentley Systems. Implement endpoint protection and email/web filtering to block malicious file attachments.

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. Identify installed Bentley View version
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Bentley View*'} | Select-Object DisplayName, DisplayVersion
    Affected if DisplayVersion exists and is less than 10.16.02
  2. Identify installed Microstation version
    Open Windows Control Panel > Programs and Features, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Microstation*'} | Select-Object DisplayName, DisplayVersion
    Affected if DisplayVersion exists and is less than 10.16.02
  3. Check for Bentley View via installed executable
    Search forbentleyview.exe in common installation paths: C:\Program Files\Bentley\View*\bentleyview.exe or C:\Program Files (x86)\Bentley\View*\bentleyview.exe. Right-click the executable and select Properties > Details to view the File Version
    Affected if Executable found with version less than 10.16.02
  4. Check for Microstation via installed executable
    Search for Microstation.exe in common installation paths: C:\Program Files\Bentley\MicroStation*\Microstation.exe or C:\Program Files (x86)\Bentley\MicroStation*\Microstation.exe. Right-click the executable and select Properties > Details to view the File Version
    Affected if Executable found with version less than 10.16.02
  5. Confirm JT file handling capability
    Check if the application has JT file type associations or if users routinely open .jt files: Look for .jt file association in Windows Default Programs, or search for .jt files on the system to gauge potential exposure
    Affected if JT file handling is enabled and the Bentley product version is below 10.16.02

You are affected if either Bentley View or Microstation is installed with a version number below 10.16.02 and the system handles 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

Users should avoid opening JT files from untrusted sources. Apply vendor patches when released by Bentley Systems. Implement endpoint protection and email/web filtering to block malicious file attachments.

Recommended fix High confidence

10.16.02

  1. Obtain the fixed version 10.16.02 from Bentley's official website or authorized distribution channel
  2. Ensure all running instances of Bentley View or MicroStation are closed
  3. Run the installer for version 10.16.02
  4. Follow the installation wizard prompts to complete the update
  5. Verify the installed version matches the fixed release (10.16.02)

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

Fix this in Bentley View Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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