dbcve.org
MicrostationApplication · Bentley

CVE-2022-28302

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. Crafted data in an IFC file can trigger a read past the end of an allocated buffer. An attacker can leverage this to execute code in the context of the current process. Was ZDI-CAN-16446.

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's IFC file parser. Crafted malicious IFC data triggers an out-of-bounds read during parsing, allowing an attacker to read past the end of an allocated buffer. This can be leveraged to achieve arbitrary code execution in the context of the current process. User interaction is required (opening a malicious IFC file).

MitigationUpdate to the patched Bentley MicroStation version. Avoid opening IFC files from untrusted sources. Implement network/email filtering to block untrusted file attachments.

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 for Bentley MicroStation or Bentley View in the installed programs list (Control Panel > Programs and Features, or use 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell)
    Affected if Neither MicroStation nor MicroStation View is installed, then the vulnerability does not apply to this system
  2. Determine installed version
    Run the application and check Help > About, or locate the executable (typically in C:\Program Files\Bentley\MicroStation\ or C:\Program Files\Bentley\View\) and right-click > Properties > Details to see the File Version
    Affected if The installed version is earlier than 10.16.03 (e.g., 10.16.00, 10.15.x, etc.)
  3. Verify IFC module availability
    Attempt to import or open an IFC file in the installed Bentley application (File > Import > IFC, or check IFC import options under DGN Options)
    Affected if The IFC import/parsing capability is present and functional, meaning the vulnerable code path exists in the environment

The system is affected if either Bentley MicroStation or Bentley View is installed with a version lower than 10.16.03 and the IFC file parsing feature is available and being used.

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

Update to the patched Bentley MicroStation version. Avoid opening IFC files from untrusted sources. Implement network/email filtering to block untrusted file attachments.

Recommended fix High confidence

MicroStation CONNECT 10.16.03 or later

  1. 1. Ensure all users close any running instances of MicroStation or MicroStation View.
  2. 2. Backup any critical project files and user preferences as a precautionary measure.
  3. 3. Download MicroStation CONNECT version 10.16.03 or later from the official Bentley Systems website (www.bentley.com).
  4. 4. Run the installer with administrator privileges.
  5. 5. Follow the on-screen installation prompts to complete the upgrade.
  6. 6. After installation, verify the version by opening MicroStation and checking Help > About MicroStation to confirm version 10.16.03 or higher is installed.

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

Fix this in Microstation Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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