CVE-2021-46635
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-15507.
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 during DGN file parsing. Specifically, crafted data in a malicious DGN file can trigger a write operation past the end of an allocated buffer, allowing remote code execution in the context of the current user process.
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 for Bentley MicroStation or Bentley View installation by examining Program Files directories (typically C:\Program Files\Bentley\MicroStation or C:\Program Files\Bentley\View) or by running 'wmic product get name,version' to list installed Bentley softwareAffected if Bentley MicroStation, MicroStation Connect, or Bentley View is installed
-
Check product versionRight-click the main executable (MicroStation.exe or BentleyView.exe), select Properties, and view the File Version under the Details tab. Alternatively, run 'wmic product where "name like '%MicroStation%' or name like '%View%'" get name,version'Affected if Version is below 10.16.02 for MicroStation/View, or version is 10.16.0.80 or below for MicroStation Connect
-
Confirm vulnerability scopeThe vulnerability is triggered when parsing malicious DGN files. Users who open DGN files from untrusted sources with an affected version are vulnerable. No special configuration or feature toggle needs to be enabled - the flaw exists in the DGN parsing code itself.Affected if Affected version is installed and users process DGN files with the software
You are affected if you have Bentley MicroStation, MicroStation Connect, or Bentley View installed with a version below 10.16.02 (or 10.16.0.80 or below for Connect) and users open DGN files with that software.
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.02
Apply the vendor-supplied patch for Bentley MicroStation CONNECT. Until patched, restrict handling of DGN files from untrusted sources and educate users about not opening suspicious file attachments.
MicroStation and MicroStation View: upgrade to 10.16.02 or later; MicroStation Connect: upgrade to 10.16.0.81 or later (or 10.16.02)
- 1. Identify the exact MicroStation product and version currently installed (MicroStation, MicroStation Connect, or MicroStation View)
- 2. Download the fixed version from the official Bentley website or through your Bentley account
- 3. For MicroStation and MicroStation View: upgrade to version 10.16.02 or later
- 4. For MicroStation Connect: upgrade to version 10.16.0.81 or later (or version 10.16.02 which contains the fix)
- 5. Verify the upgrade was successful by checking the version in the application's About section
- 6. Test that DGN files open correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46635 — 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-46635 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