dbcve.org
MicrostationApplication · Bentley

CVE-2021-46562

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 read 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-14987.

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

Out-of-bounds read vulnerability in Bentley MicroStation CONNECT when parsing malicious JT files. The JT file parser fails to properly validate buffer boundaries, allowing a crafted file to read past the end of an allocated buffer. This can be leveraged for arbitrary code execution in the context of the current process.

MitigationApply vendor patch when available; until then, avoid opening JT files from untrusted sources and implement network-level controls to block delivery of suspicious file attachments.

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
    Open the application and navigate to Help > About Bentley [Product Name], or right-click the executable and view Properties > Details to find the version number
    Affected if The product is Bentley MicroStation, MicroStation Connect, or Bentley View with a version lower than 10.16.02 (or <= 10.16.0.80 for Connect)
  2. Confirm the product name and exact version
    Locate the exact version string (such as 10.16.00.xx or similar) from the About dialog or file properties
    Affected if The version falls outside the fixed releases: MicroStation/View < 10.16.02 or Connect <= 10.16.0.80
  3. Determine if JT file parsing is in use
    Check if users or automated processes open or import JT files within the environment. Inspect recent file access logs or the application Recent Files list for .jt file extensions
    Affected if JT files are opened, imported, or processed by the affected software

You are affected if you have an installed version of MicroStation, MicroStation Connect, or Bentley View that is below the fixed releases AND the software processes JT files from any source.

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 patch when available; until then, avoid opening JT files from untrusted sources and implement network-level controls to block delivery of suspicious file attachments.

Recommended fix High confidence

MicroStation 10.16.02 or higher / MicroStation Connect version > 10.16.0.80

  1. 1. Identify the current MicroStation or MicroStation Connect version installed on the system
  2. 2. Navigate to the official Bentley support website or software update mechanism
  3. 3. Download MicroStation version 10.16.02 or higher (or MicroStation Connect version greater than 10.16.0.80)
  4. 4. Before installing, backup all critical project files and configurations
  5. 5. Close any running MicroStation instances
  6. 6. Run the installer with administrator privileges
  7. 7. Follow the on-screen installation prompts to complete the upgrade
  8. 8. After installation, verify the new version by checking 'Help' > 'About MicroStation'
Caveat Users should verify compatibility of custom workspaces, VBA macros, and third-party add-ons with version 10.16.02 before deploying in production environments

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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