dbcve.org
MicrostationApplication · Bentley

CVE-2021-46571

HIGH · 7.8 CVSS v3.1 Published 2022-02-18
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.16.0.80. 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-15365.

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

Memory corruption vulnerability in Bentley View's JT file parser where the parser fails to validate object existence before performing operations on it. An attacker can exploit this by crafting a malicious JT file that, when opened by a user, allows arbitrary code execution in the context of the current process.

MitigationDo not open untrusted JT files until Bentley releases a patch. Apply vendor security updates as soon as available. Consider running Bentley View in restricted environments or sandboxes as a defense-in-depth measure.

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
MicrostationApplication
Affected:< 10.16.02
Microstation ConnectApplication
Affected:<= 10.16.0.80
ViewApplication
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 the installed Bentley product
    Check which Bentley application is installed: Bentley View, Bentley Microstation, or Bentley Microstation Connect. This can be verified through the Windows Programs and Features list, the application shortcut, or by launching the application and noting its name.
    Affected if The product is Bentley View, Bentley Microstation, or Bentley Microstation Connect.
  2. Determine the installed version number
    Open the Bentley application and navigate to Help > About, or right-click the executable file and select Properties > Details to view the product version. Alternatively, check the version in the Windows Programs and Features list.
    Affected if The exact version number cannot be determined.
  3. Compare version against affected ranges
    Compare your installed version to the following vulnerable ranges: Bentley Microstation versions below 10.16.02, Bentley Microstation Connect versions 10.16.0.80 or below, and Bentley View versions below 10.16.02.
    Affected if The installed version falls within any of these ranges: Microstation < 10.16.02, Microstation Connect <= 10.16.0.80, or View < 10.16.02.
  4. Confirm JT file parsing is accessible
    Verify that the application can open or process JT files. Attempt to open a JT file through File > Open or drag a JT file into the application. The vulnerability exists in the JT file parser component.
    Affected if JT files can be opened or processed by the application.

You are affected if you are running Bentley View, Microstation, or Microstation Connect at a version below 10.16.02 (or 10.16.0.80 or below for Connect edition) and the application can open 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

Do not open untrusted JT files until Bentley releases a patch. Apply vendor security updates as soon as available. Consider running Bentley View in restricted environments or sandboxes as a defense-in-depth measure.

Recommended fix High confidence

Microstation: 10.16.02 or later | Microstation Connect: 10.16.0.80 or later (10.16.02 recommended) | View: 10.16.02 or later

  1. 1. Identify the installed Bentley product (Microstation, Microstation Connect, or View) and current version
  2. 2. Navigate to the Bentley software download portal or check for updates within the application
  3. 3. Download version 10.16.02 or later for Microstation and View products
  4. 4. For Microstation Connect, download version 10.16.0.80 or later (10.16.02 recommended)
  5. 5. Apply the update following standard Bentley installation procedures
  6. 6. Verify the installed version matches or exceeds the fixed release

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

Fix this in Microstation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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