CVE-2021-46589
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 disclose sensitive information 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. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-15383.
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 confidenceThis is a buffer over-read vulnerability in Bentley MicroStation CONNECT when parsing DGN files. The lack of proper validation of user-supplied data allows reading past the end of an allocated buffer, enabling disclosure of sensitive information. Exploitation requires the user to open a malicious DGN file, and this vulnerability can be chained with other flaws for arbitrary code execution.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 product and versionOpen the Bentley application, go to Help > About or check Programs and Features in Control Panel for the exact version number (for MicroStation, MicroStation Connect, or Bentley View)Affected if The installed version is MicroStation < 10.16.02, MicroStation Connect = 10.16.0.80, or Bentley View < 10.16.02
-
Verify DGN file handling is activeCheck if the application has been used to open DGN files recently, or review recent file associations in the application settings showing DGN as an enabled file typeAffected if DGN file handling is enabled and the application processes DGN files
-
Check file preview or parsing settingsReview application preferences for automatic file preview, quick preview, or background parsing features that process DGN files upon file accessAffected if Automatic preview or background parsing of DGN files is enabled
You are affected if you have MicroStation < 10.16.02, MicroStation Connect = 10.16.0.80, or Bentley View < 10.16.02 installed with DGN file handling enabled.
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 MicroStation CONNECT. Until patched, restrict file handling to trusted DGN sources and consider disabling automatic file preview/parsing features.
MicroStation 10.16.02 or later / MicroStation Connect 10.16.0.81 or later / View 10.16.02 or later
- 1. Identify the current Bentley MicroStation, MicroStation Connect, or View version by opening the application and checking Help > About
- 2. Navigate to the official Bentley website (www.bentley.com) and locate the downloads or support section
- 3. Download MicroStation version 10.16.02 or later (or MicroStation Connect version 10.16.0.81 and later)
- 4. Close all running MicroStation applications
- 5. Run the downloaded installer and follow the on-screen prompts to complete the update
- 6. Verify the installation was successful by checking the version number in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46589 — 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-46589 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