dbcve.org
MicrostationApplication · Bentley

CVE-2021-46585

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

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 MicroStation CONNECT's JT file parser. The vulnerability results from insufficient validation of user-supplied data length before copying to a stack-based buffer, allowing remote code execution via malicious JT files.

MitigationAvoid opening untrusted or unverified JT files. Update to the patched version when released by Bentley. Apply vendor-supplied security updates promptly.

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
    Check Programs and Features or the application about dialog to determine if MicroStation, MicroStation Connect, or Bentley View is installed
    Affected if Any of these three products are installed
  2. Determine the exact version number
    Open the application, go to Help > About or check the program's properties in Add/Remove Programs to find the installed version string
    Affected if Version is MicroStation < 10.16.02, MicroStation Connect = 10.16.0.80, or View < 10.16.02
  3. Verify JT file parsing capability is present
    Check if the application can open or preview JT files - look for .jt file association or try opening a JT file in the application
    Affected if The application can process JT files and the version falls within the affected range
  4. Confirm product edition
    Confirm whether the installation is MicroStation (standard), MicroStation Connect (subscription), or Bentley View (viewer)
    Affected if Any edition matches the version criteria in step 2

A user is affected if they have MicroStation versions below 10.16.02, MicroStation Connect version 10.16.0.80, or Bentley View versions below 10.16.02 installed and the JT file parser is available in their environment.

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

Avoid opening untrusted or unverified JT files. Update to the patched version when released by Bentley. Apply vendor-supplied security updates promptly.

Recommended fix High confidence

MicroStation 10.16.02 or later / MicroStation Connect version newer than 10.16.0.80

  1. Identify the specific MicroStation product variant installed (MicroStation, MicroStation Connect, or MicroStation View)
  2. Check the current installed version of the software
  3. Download and install MicroStation version 10.16.02 or later, or MicroStation Connect version newer than 10.16.0.80
  4. Verify the installation completed successfully

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

Fix this in Microstation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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