dbcve.org
MicrostationApplication · Bentley

CVE-2021-46572

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 MicroStation CONNECT 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. 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-15366.

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 in Bentley MicroStation CONNECT allows remote attackers to execute arbitrary code via crafted JT files. The flaw exists in JT file parsing where crafted data triggers a write past the end of an allocated buffer, enabling code execution in the context of the current process. User interaction is required (opening malicious file).

MitigationApply vendor patches from Bentley for MicroStation CONNECT. Until patched, avoid opening untrusted JT files from unknown or 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
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 MicroStation product and version
    Open MicroStation, go to Help > About MicroStation, or check Add/Remove Programs for 'Bentley MicroStation CONNECT', 'Bentley MicroStation', or 'Bentley View'. Note the exact version number displayed.
    Affected if The installed version is MicroStation CONNECT version 10.16.0.80, or MicroStation/View versions below 10.16.02.
  2. Confirm the product name matches affected software
    Review the product name from the About dialog or installation list. This CVE affects three products: MicroStation CONNECT, MicroStation, and Bentley View.
    Affected if The product is any of these three Bentley applications and the version falls within the affected ranges.
  3. Determine if JT file handling is in use
    Check if users in your environment commonly open or work with JT files, or search for .jt file associations in the system. Look at recent file access logs or the application's recent files list.
    Affected if The application is used to open or process JT files, as the vulnerability is triggered during JT file parsing.
  4. Assess user exposure to untrusted JT files
    Review file handling practices: check if users receive JT files from external sources, examine email attachments, or monitor file downloads from untrusted sources.
    Affected if Users open JT files from unknown or untrusted sources without prior security validation.

You are affected if you have MicroStation CONNECT version 10.16.0.80, or MicroStation/Bentley View versions below 10.16.02, and users in your environment open JT files from untrusted sources.

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 vendor patches from Bentley for MicroStation CONNECT. Until patched, avoid opening untrusted JT files from unknown or untrusted sources.

Recommended fix High confidence

MicroStation 10.16.02 or later / MicroStation Connect version newer than 10.16.0.80

  1. 1. Verify the current installed version of Bentley MicroStation or MicroStation Connect by opening the application and navigating to Help > About MicroStation
  2. 2. Download the fixed version of MicroStation (10.16.02 or later) or MicroStation Connect from the official Bentley website at www.bentley.com
  3. 3. Ensure all work is saved and close any open MicroStation instances
  4. 4. Run the installer for the new version and follow the on-screen prompts to complete the upgrade
  5. 5. After installation, verify the new version by checking Help > About MicroStation to confirm version 10.16.02 or higher is installed
  6. 6. Test that JT file parsing works correctly with the updated version

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

Fix this in Microstation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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