dbcve.org
MicrostationApplication · Bentley

CVE-2022-28641

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.34. 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. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16390.

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 remote code execution vulnerability exists in Bentley MicroStation CONNECT when parsing IFC files. The flaw stems from the application failing to validate the existence of an object before performing operations on it, leading to potential arbitrary code execution in the context of the current process. User interaction is required (opening a malicious IFC file).

MitigationApply the vendor patch from Bentley when available. Until then, instruct users to only open IFC files from trusted sources and consider implementing endpoint protection that monitors for suspicious file operations.

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 if Bentley software is installed
    Check for MicroStation or Bentley View in the system: Look in Programs and Features, or check common installation paths such as C:\Program Files\Bentley\MicroStation or C:\Program Files\Bentley\Bentley View
    Affected if Either MicroStation or Bentley View is present on the system
  2. Determine installed version
    Open the application, go to Help > About, or check the version in the software's executable properties. Compare the version number to 10.16.03
    Affected if The installed version is lower than 10.16.03 (e.g., 10.16.00, 10.15.x, etc.)
  3. Verify IFC parsing capability exists
    Confirm the IFC import/export or translator functionality is available in the installation. This is typically found under File > Import or File > Export menu as an IFC option
    Affected if The IFC file handling module is present and enabled in the application
  4. Check for recent IFC file activity
    Review the application's recent files list, Windows recent documents, or check the application's log files for IFC file operations. Also inspect file system for recently opened .ifc files in user directories
    Affected if IFC files have been opened in the vulnerable version of the software

A system is affected if Bentley MicroStation or Bentley View version lower than 10.16.03 is installed and IFC files can be parsed by the application.

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

Apply the vendor patch from Bentley when available. Until then, instruct users to only open IFC files from trusted sources and consider implementing endpoint protection that monitors for suspicious file operations.

Recommended fix High confidence

MicroStation 10.16.03 or later (or MicroStation View 10.16.03 or later)

  1. Backup any critical MicroStation files and projects before upgrading
  2. Obtain MicroStation version 10.16.03 or later from the official Bentley website (www.bentley.com) or your organization's software distribution channel
  3. Run the Bentley installer and follow the on-screen prompts to upgrade MicroStation
  4. Restart the application if prompted after installation
  5. Verify the installed version by checking Help > About MicroStation to confirm version 10.16.03 or later is installed
  6. Exercise caution when opening IFC files from untrusted sources, even after patching

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

Fix this in Microstation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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