dbcve.org
MicrostationApplication · Bentley

CVE-2022-28311

HIGH · 7.8 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 10.16.03 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
This vulnerability allows remote attackers to execute arbitrary code on affected installations of Bentley MicroStation CONNECT 10.16.02.034. 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 DXF files. Crafted data in a DXF file can trigger a read 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-16341.

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 confidence

An out-of-bounds read vulnerability in Bentley MicroStation CONNECT's DXF file parser allows remote attackers to execute arbitrary code via a specially crafted DXF file that triggers a read past the end of an allocated buffer, requiring the victim to open the malicious file.

MitigationUsers should avoid opening untrusted DXF files until a vendor patch is available; the vulnerability stems from insufficient bounds checking during DXF parsing that must be corrected in the parsing logic.

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
MicrostationApplication
Affected:< 10.16.03
ViewApplication
Affected:< 10.16.03

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Bentley software is installed
    Check system for Bentley MicroStation CONNECT or Bentley View installation by looking for the application in Program Files (typically C:\Program Files\Bentley\MicroStation CONNECT Edition\) or via Windows Add/Remove Programs
    Affected if Either MicroStation CONNECT or Bentley View is present on the system
  2. Identify installed version
    Locate the application executable (typically MicroStation.exe or BentleyView.exe) and check its version property via right-click > Properties > Details, or use a system inventory tool to query the installed version
    Affected if Version cannot be determined or is below 10.16.03
  3. Compare version to affected range
    Compare the installed version number (for example, 10.16.00.80 or 10.16.02) against the safe version 10.16.03 - note that any version < 10.16.03 is affected
    Affected if Installed version is less than 10.16.03 (for example, 10.16.02, 10.16.01, 10.16.00, or any 10.15.x release)
  4. Assess DXF file handling exposure
    Verify the system can process DXF files - the vulnerability triggers when opening a malicious DXF file, so any user who can open DXF files in MicroStation or View is potentially affected
    Affected if Users can open or import DXF files in the installed Bentley product

Your environment is affected if Bentley MicroStation CONNECT or Bentley View is installed with any version prior to 10.16.03, as the vulnerable DXF parser code is present in those versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.16.03 or later
Fixed in 10.16.03
Interim mitigation

Users should avoid opening untrusted DXF files until a vendor patch is available; the vulnerability stems from insufficient bounds checking during DXF parsing that must be corrected in the parsing logic.

Recommended fix High confidence

10.16.03 or later

  1. 1. Back up all critical project files and user preferences before updating.
  2. 2. Navigate to the official Bentley Systems support portal or software distribution channel.
  3. 3. Download MicroStation CONNECT version 10.16.03 or later (or MicroStation View version 10.16.03 or later).
  4. 4. Close all running instances of MicroStation or MicroStation View.
  5. 5. Run the installer with appropriate administrative privileges.
  6. 6. Follow the installation wizard prompts to complete the update.
  7. 7. After installation, verify the version by checking About MicroStation to confirm version 10.16.03 or higher is installed.
  8. 8. Test that DXF files open correctly to confirm the vulnerability is remediated.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Microstation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28311 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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