dbcve.org
MicrostationApplication · Bentley

CVE-2022-28318

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 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-16379.

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 overflow vulnerability exists in Bentley MicroStation CONNECT's IFC file parser. When parsing a specially crafted IFC file, the parser writes data past the end of an allocated buffer, allowing an attacker to execute arbitrary code in the context of the current user process.

MitigationUntil an official patch is available, restrict user ability to open untrusted IFC files. Implement file origin verification and consider running MicroStation in an isolated environment to limit exploit impact.

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. Verify Bentley MicroStation or View is installed
    Check the installed programs list in Windows Control Panel > Programs and Features, or use the command 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName' to list installed software
    Affected if Either Bentley MicroStation CONNECT or Bentley View appears in the installed programs list
  2. Determine the installed version of MicroStation or View
    Open the application, then go to Help > About Bentley MicroStation, or right-click the application shortcut and select Properties to view version information. Alternatively, check the program's executable file properties
    Affected if The version number displayed is lower than 10.16.03 (for example, 10.16.00, 10.15.x, or earlier)
  3. Assess IFC file handling exposure
    Determine if the system or users have the ability to open IFC files from untrusted or external sources. Check if IFC file associations are enabled and review file download/open workflows in your environment
    Affected if Users can open IFC files from untrusted or unknown sources without prior validation or scanning

You are affected if MicroStation or View version is below 10.16.03 AND users in your environment can open IFC files from untrusted or external sources.

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

Until an official patch is available, restrict user ability to open untrusted IFC files. Implement file origin verification and consider running MicroStation in an isolated environment to limit exploit impact.

Recommended fix High confidence

MicroStation CONNECT and View 10.16.03

  1. 1. Back up all critical project files and configurations before proceeding with the upgrade.
  2. 2. Obtain MicroStation CONNECT version 10.16.03 or later from the official Bentley Systems download portal.
  3. 3. Uninstall the current version of MicroStation or View from the system.
  4. 4. Install version 10.16.03 or newer of the affected product.
  5. 5. Verify the installation by checking Help > About MicroStation/View to confirm the version number.
  6. 6. Test critical IFC file workflows to ensure the update does not impact existing workflows.
Caveat Review Bentley's release notes for 10.16.03 to check for any compatibility changes or feature modifications that may affect existing workflows

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-28318 — 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-28318 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