dbcve.org
MicrostationApplication · Bentley

CVE-2021-46576

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

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 10.16.0.80 allows remote code execution through malicious JT files. The flaw exists in JT file parsing where crafted data triggers a write past the end of an allocated buffer, enabling arbitrary code execution in the context of the current process when a user opens a malicious JT file.

MitigationApply the vendor patch from Bentley for MicroStation CONNECT. Until patched, instruct users to avoid opening 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
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 installed Bentley product
    Open Windows Control Panel > Programs and Features, or use 'Get-ItemProperty' PowerShell command to list installed Bentley software. Look for 'Bentley MicroStation', 'Bentley MicroStation CONNECT', or 'Bentley View'
    Affected if No Bentley product is installed - not affected; product found - continue to version check
  2. Determine product version
    Right-click the installed Bentley program in Programs and Features and select 'Change' or 'Properties' to view the version. Alternatively, locate the program's executable (typically in C:\Program Files\Bentley\MicroStation or C:\Program Files\Bentley\View) and check file properties for version information
    Affected if Cannot determine version - further investigation needed
  3. Compare version to affected ranges
    Match your installed product and version against: MicroStation < 10.16.02, MicroStation CONNECT = 10.16.0.80, or View < 10.16.02
    Affected if Installed version matches one of these ranges - likely affected
  4. Verify JT file handling capability
    Open the Bentley application and attempt to open or import a JT file (.jt extension) through File > Open or File > Import to confirm JT parsing functionality is accessible
    Affected if JT file handling is available and vulnerable version is installed - affected

User is affected if Bentley MicroStation, MicroStation CONNECT (version 10.16.0.80), or Bentley View is installed with a version below 10.16.02 and the application can open or parse 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

Apply the vendor patch from Bentley for MicroStation CONNECT. Until patched, instruct users to avoid opening JT files from untrusted sources.

Recommended fix High confidence

MicroStation/View: 10.16.02 or later | MicroStation Connect: 10.16.0.81 or later

  1. 1. Backup all critical JT files and current MicroStation configurations
  2. 2. Obtain the latest version of MicroStation (10.16.02 or later) or MicroStation Connect from the official Bentley website or licensed distribution channel
  3. 3. Uninstall the current MicroStation or MicroStation Connect installation
  4. 4. Install the upgraded version (10.16.02 or later for MicroStation/View; 10.16.0.81 or later for Connect)
  5. 5. Verify the installation was successful by launching the application
  6. 6. Test parsing of legitimate JT files to confirm functionality
Caveat Review Bentley release notes for any feature changes or workflow adjustments between versions

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

Fix this in Microstation Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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