CVE-2021-46646
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 · uneditedThis 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 DGN files. Crafted data in a DGN 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-15532.
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 confidenceA buffer overflow vulnerability exists in Bentley MicroStation CONNECT 10.16.0.80 when parsing DGN files. Specifically, crafted data within a malicious DGN file triggers a write operation past the end of an allocated buffer, allowing an attacker to execute arbitrary code in the context of the current user process. Exploitation requires user interaction—opening a malicious DGN file or visiting a webpage hosting the crafted file.
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< 10.16.02< 10.16.0.80< 10.16.02CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bentley productCheck the system for Bentley MicroStation, MicroStation CONNECT, or Bentley View applications. Look in Program Files for Bentley folder, or check the application executable properties (right-click MicroStation.exe or BentleyView.exe and select Properties > Details)Affected if Any of these three products (MicroStation, MicroStation CONNECT, or Bentley View) are installed
-
Determine installed versionOpen the application, go to Help > About, or right-click the executable and check Properties > Details for the File VersionAffected if Version is < 10.16.02 for MicroStation or Bentley View, or < 10.16.0.80 for MicroStation CONNECT
-
Confirm DGN file handling capabilityAttempt to open a standard DGN file or check file associations in the application. DGN is the native MicroStation format and is typically handled by defaultAffected if DGN file parsing is enabled (default state) and a vulnerable version is installed
-
Check for recent security updatesLook in the application Help > Check for Updates or Bentley Subscriptions for installed hotfixes/patches. Alternatively, check Add/Remove Programs for recent Bentley updatesAffected if No patches have been installed after the vulnerable version and the version remains below the fixed releases
A user is affected if they have MicroStation, MicroStation CONNECT, or Bentley View installed with a version below 10.16.02 (or 10.16.0.80 for CONNECT) and the application can parse DGN files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.16.0.8010.16.02
Apply the vendor patch or upgrade to a patched version of MicroStation CONNECT. Until patched, avoid opening DGN files from untrusted sources and disable automatic file opening in the application.
MicroStation and View: upgrade to version 10.16.02 or later; MicroStation Connect: upgrade to version 10.16.0.80 or later
- 1. Close any running instances of Bentley MicroStation, MicroStation Connect, or MicroStation View
- 2. Obtain the latest version of the affected Bentley product from the official Bentley systems website or your Bentley software distributor
- 3. Run the installer for the fixed version (10.16.02 or 10.16.0.80, depending on your product)
- 4. Follow the installation wizard prompts to complete the update
- 5. Restart your system after installation completes
- 6. Verify the installed version matches the fixed release (10.16.02 for MicroStation/View, or 10.16.0.80 for MicroStation Connect)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-46646 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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