CVE-2021-46564
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 JT files. Crafted data in a JT 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-15023.
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 confidenceBuffer overflow vulnerability in Bentley MicroStation CONNECT when parsing JT files. Crafted JT file containing malformed data triggers an out-of-bounds write past the end of an allocated buffer during parsing, allowing attackers to execute arbitrary code in the context of the current process. Exploitation requires user interaction to open a malicious JT 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 if Bentley MicroStation, MicroStation CONNECT, or Bentley View is installed on the system by looking in installed programs or the application directoryAffected if One of these three products is present
-
Determine the installed version numberOpen the Bentley application, then go to Help > About or use the application menu to find the version information. Alternatively, check the program's properties in Add/Remove ProgramsAffected if The version is lower than 10.16.02 for MicroStation or Bentley View, or 10.16.0.80 or lower for MicroStation CONNECT
-
Confirm the software can parse JT filesVerify the installation includes JT file parsing capability by attempting to open a JT file or checking file association settings for .jt extensionAffected if JT file handling is enabled and the version is within the affected range
-
Verify the vulnerability trigger conditionThe flaw requires a user to open a malicious crafted JT file. Check whether users in your environment commonly open JT files from external or untrusted sourcesAffected if Users open JT files and the version is within the affected range
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 for CONNECT) and users open JT 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
Do not open untrusted JT files from unknown sources. Apply vendor patches from Bentley when available. Consider implementing file sandboxing or disabling JT file preview until patched.
MicroStation / MicroStation Connect / View: version 10.16.02 or later
- Upgrade MicroStation (including MicroStation Connect) to version 10.16.02 or later
- If using View, upgrade to version 10.16.02 or later
- Avoid opening untrusted JT files from unknown or untrusted sources until the patch is applied
- Verify the upgrade by checking Help > About MicroStation to confirm the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46564 — 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-46564 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