dbcve.org
MicrostationApplication · Bentley

CVE-2022-28647

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.2.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 IFC files. Crafted data in an IFC 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-16573.

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

A buffer over-read vulnerability exists in Bentley MicroStation CONNECT during IFC file parsing. The vulnerability allows reading past the end of an allocated buffer when processing crafted IFC files, leading to arbitrary code execution in the context of the current process. User interaction is required (opening a malicious IFC file).

MitigationAvoid opening untrusted or unverified IFC files. Apply vendor-provided security patches or updates for Bentley MicroStation CONNECT when released. Implement file sandboxing or disable IFC file processing for untrusted sources.

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. Identify installed Bentley product
    Check if Bentley MicroStation CONNECT or Bentley View is installed on the system. Look for the application in the installed programs list or in the installation directory (typically C:\Program Files\Bentley\MicroStation or C:\Program Files\Bentley\View).
    Affected if Either Bentley MicroStation CONNECT or Bentley View is present on the system.
  2. Determine installed version
    Open Bentley MicroStation or Bentley View, then navigate to Help > About or use the product's About dialog to display the exact version number. Alternatively, check the program's properties in the Windows installation directory or in the Windows Registry under HKLM\SOFTWARE\Bentley\MicroStation or HKLM\SOFTWARE\Bentley\View.
    Affected if A version number is found for either product.
  3. Compare version against affected range
    Compare your installed version number to the affected threshold of 10.16.03. Versions below 10.16.03 (such as 10.16.02, 10.16.01, 10.16.00, or earlier) are within the vulnerable range.
    Affected if The installed version is less than 10.16.03.
  4. Assess IFC file processing exposure
    Determine if the product is used to open or process IFC (Industry Foundation Classes) files, which is the file type that triggers the vulnerability. This can be verified by checking recent file access history, file associations for .ifc files, or user workflow documentation.
    Affected if The product is used to open IFC files and the version is below 10.16.03.

You are affected if Bentley MicroStation CONNECT or Bentley View is installed with a version lower than 10.16.03 and you process IFC files with the vulnerable software.

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

Avoid opening untrusted or unverified IFC files. Apply vendor-provided security patches or updates for Bentley MicroStation CONNECT when released. Implement file sandboxing or disable IFC file processing for untrusted sources.

Recommended fix High confidence

MicroStation CONNECT / View version 10.16.03

  1. 1. Back up all critical data and project files before upgrading
  2. 2. Download MicroStation CONNECT version 10.16.03 or later from the official Bentley Systems website
  3. 3. Uninstall the current version of MicroStation or View via Windows Control Panel
  4. 4. Install the downloaded version 10.16.03 or newer
  5. 5. Verify the installation by checking Help > About MicroStation to confirm the version number
  6. 6. Test critical IFC file workflows to ensure functionality is maintained
Caveat Upgrade should be low-risk; verify custom configurations and add-ins are compatible with 10.16.03 in a test environment before production deployment

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

Fix this in Microstation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28647 — 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-28647 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