dbcve.org
Bentley ViewApplication · Bentley

CVE-2021-34941

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 proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15040.

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

Stack-based buffer overflow in Bentley View's JT file parser due to insufficient validation of user-supplied data length before copying to a stack buffer, allowing remote code execution via malicious JT file.

MitigationRestrict opening of untrusted JT files and apply vendor patch when available; implement endpoint detection and file sandboxing as compensating controls.

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 software
    Check for Bentley View or MicroStation installation in the system. Common paths: C:\Program Files\Bentley\View\ or C:\Program Files\Bentley\MicroStation\. Also query Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Bentley View' or 'MicroStation'.
    Affected if Neither Bentley View nor MicroStation is installed on the system.
  2. Determine Bentley View version
    Locate the main executable (typically BentleyView.exe) in the installation directory. Right-click the executable, select Properties, and check the 'Details' tab for the Product version field. Alternatively, run: wmic product where "name like 'Bentley View'" get version
    Affected if Bentley View is installed and its version is lower than 10.16.02.
  3. Determine MicroStation version
    Locate the main executable (MicroStation.exe) in the installation directory. Right-click the executable, select Properties, and check the 'Details' tab for the Product version field. Alternatively, run: wmic product where "name like 'MicroStation'" get version
    Affected if MicroStation is installed and its version is lower than 10.16.02.
  4. Verify JT file parsing capability
    Check if the JT file parser component is loaded or enabled. This may be indicated by the presence of JT-related DLL files in the installation directory (e.g., jt*.* files) or by attempting to open a JT file in the software to confirm the parser is active.
    Affected if The JT file parser component is present and functional in the affected software version.

The system is affected if either Bentley View or MicroStation is installed with a version lower than 10.16.02 and the JT file parser component is present and operational.

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

Restrict opening of untrusted JT files and apply vendor patch when available; implement endpoint detection and file sandboxing as compensating controls.

Recommended fix High confidence

10.16.02

  1. 1. Close all instances of Bentley View or MicroStation running on the system
  2. 2. Download the patched version (10.16.02) from the official Bentley website or your organization's software distribution point
  3. 3. Run the installer for version 10.16.02
  4. 4. Follow the on-screen installation prompts to complete the upgrade
  5. 5. Restart the application after installation completes
  6. 6. Verify the installed version matches 10.16.02 or later by checking the About/Help section

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-34941 — 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-34941 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