CVE-2021-46606
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 BMP images. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15400.
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 heap-based buffer overflow vulnerability exists in Bentley MicroStation CONNECT during BMP image parsing. The application fails to validate the length of user-supplied data before copying it into a heap buffer, allowing an attacker to overflow the buffer and achieve arbitrary code execution in the context of the current process. Exploitation requires the victim to open a malicious BMP file or visit a malicious page.
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 the installed Bentley productOpen Bentley MicroStation CONNECT, Bentley MicroStation, or Bentley View. Go to Help > About to display the product name and version number.Affected if The product is Bentley MicroStation (any version), Bentley MicroStation Connect, or Bentley View.
-
Determine the exact version numberIn the About dialog, record the full version string (for example: 10.16.0.80, 10.16.01.00, etc.).Affected if Version cannot be determined or is below 10.16.02 for MicroStation/View, or 10.16.0.80 for MicroStation Connect.
-
Compare installed version against affected rangesFor MicroStation or Bentley View: check if version is less than 10.16.02. For MicroStation Connect: check if version is 10.16.0.80 or lower.Affected if Version is < 10.16.02 (MicroStation/View) or <= 10.16.0.80 (MicroStation Connect).
-
Assess BMP file handling exposureDetermine whether the application is used to open or preview BMP image files, or if untrusted BMP files could be processed through the application.Affected if BMP files can be opened or processed by the affected application version.
A user is affected if they have MicroStation, MicroStation Connect, or Bentley View at version 10.16.0.80 or below (Connect) or below 10.16.02 (MicroStation/View), and the application processes BMP 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
Update to a patched version of Bentley MicroStation CONNECT when available. Avoid opening untrusted BMP files or visiting untrusted websites until the patch is applied.
MicroStation/MicroStation Connect/MicroStation View: version 10.16.02 or later
- 1. Verify the current installed version of Bentley MicroStation by accessing Help > About MicroStation
- 2. For MicroStation (standalone): Upgrade to version 10.16.02 or later
- 3. For MicroStation Connect: Upgrade to version 10.16.0.80以上的版本 (10.16.02 or later recommended)
- 4. For MicroStation View: Upgrade to version 10.16.02 or later
- 5. After upgrading, verify the new version by checking Help > About MicroStation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46606 — 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-46606 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