CVE-2021-46620
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 FBX 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-15414.
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 · moderate confidenceAn out-of-bounds read vulnerability exists in Bentley MicroStation CONNECT 10.16.0.80 when parsing FBX files. The lack of proper validation of user-supplied data during FBX parsing allows attackers to read past the end of an allocated buffer, enabling sensitive information disclosure. This can be chained with other vulnerabilities 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 productCheck Windows Programs and Features or the application's About section for Bentley MicroStation, MicroStation Connect, or Bentley ViewAffected if Any of these three products is installed
-
Determine installed versionOpen the application, go to Help > About, or check the program's version property in Windows. Note the full version number (e.g., 10.16.0.80)Affected if Version is below 10.16.02 for MicroStation/View, or 10.16.0.80 or lower for MicroStation Connect
-
Confirm FBX parsing capabilityVerify that the installation includes FBX import functionality - check if FBX file type appears in the application's supported import formats or file open dialogsAffected if FBX file handling is present in the installation
-
Check for recent FBX file accessReview recent file access logs or the application's recent files list for .fbx files opened from untrusted sourcesAffected if Users have opened FBX files with this version of the software
You are affected if you have MicroStation, MicroStation Connect, or Bentley View installed with a version below 10.16.02 (or 10.16.0.80 or lower for Connect) and the FBX parsing feature is available, as the vulnerable code executes when opening malicious FBX 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.02
Apply the vendor patch from Bentley when available. Until then, enforce strict policies against opening untrusted FBX files and consider network-based file inspection controls.
MicroStation 10.16.02 / MicroStation Connect 10.16.0.81 or later
- 1. Close any running instances of Bentley MicroStation or MicroStation Connect
- 2. Back up your current project files and user preferences as a precaution
- 3. Navigate to the Bentley product download page or use the Bentley Softdesk/Product Select tool
- 4. Download the latest version: MicroStation 10.16.02 or MicroStation Connect 10.16.0.81 or later
- 5. Run the installer and follow the on-screen prompts to complete the upgrade
- 6. After installation, verify the version by opening MicroStation and checking Help > About MicroStation
- 7. Avoid opening untrusted FBX files from unknown sources until the update is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46620 — 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-46620 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