CVE-2021-46584
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 J2K images. Crafted data in a J2K image 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-15378.
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's J2K (JPEG 2000) image parser. When parsing specially crafted J2K image files, the application writes data past the end of an allocated buffer, allowing an attacker to execute arbitrary code in the context of the current process. Exploitation requires user interaction via opening a malicious J2K file or visiting a malicious webpage.
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 softwareCheck for Bentley MicroStation, MicroStation Connect, or Bentley View installations in Program Files or via Add/Remove Programs. Look for executables such as MicroStation.exe, BentleyView.exe, or related launcher binaries.Affected if Any of these three products are installed on the system
-
Locate version informationRight-click the main executable (MicroStation.exe, BentleyView.exe, or the MicroStation Connect launcher) and select Properties, then check the Details tab for the Product Version. Alternatively, open the application and go to Help > About to view the version.Affected if Version cannot be determined or does not match a patched release
-
Compare version to affected rangesIf the product is MicroStation (non-Connect) or Bentley View, check if version is less than 10.16.02. If the product is MicroStation Connect, check if version equals 10.16.0.80 specifically.Affected if Version is below 10.16.02 for MicroStation/Bentley View, or equals exactly 10.16.0.80 for MicroStation Connect
-
Confirm J2K file handling capabilityOpen the application and attempt to open or import a J2K/JPEG 2000 file, or check File > Open file type filters. The vulnerability exists in the J2K parser component which is part of standard image handling.Affected if The application can open or process J2K files (default behavior for most installations)
The user is affected if Bentley MicroStation, MicroStation Connect, or Bentley View is installed and the version falls within the affected ranges (MicroStation/Bentley View < 10.16.02, or MicroStation Connect = 10.16.0.80) and the application can process J2K image 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
Restrict opening of J2K files from untrusted sources and apply vendor patches when available. Consider application sandboxing or isolation for high-risk users.
MicroStation 10.16.02 or later / MicroStation Connect 10.16.0.80 to 10.16.02
- 1. Verify current MicroStation or MicroStation Connect version by navigating to the application's About dialog
- 2. Download MicroStation version 10.16.02 or later from the official Bentley Systems website
- 3. Close all running instances of MicroStation or MicroStation Connect
- 4. Run the installer with administrator privileges
- 5. Follow the on-screen installation prompts to complete the upgrade
- 6. Restart the application after installation completes
- 7. Verify the installed version shows 10.16.02 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46584 — 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-46584 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