dbcve.org
MicrostationApplication · Bentley

CVE-2022-28316

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

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 when parsing IFC files. The vulnerability allows writing past the end of an allocated buffer through crafted data within an IFC file, enabling arbitrary code execution in the context of the current user process.

MitigationApply the vendor patch when available. Until then, avoid opening untrusted or unverified IFC files, and disable automatic file opening in the application.

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 MicroStation or MicroStation View is installed
    Open Windows Control Panel > Programs and Features, or check the program installation directory (typically C:\Program Files\Bentley\MicroStation) for the application executable
    Affected if Bentley MicroStation or Bentley View is present on the system
  2. Determine the installed version number
    Right-click the MicroStation or MicroStation View executable, select Properties, and check the Version tab. Alternatively, open the application and go to Help > About MicroStation to view the exact version
    Affected if The version shown is earlier than 10.16.03 (for example, 10.16.00, 10.16.01, 10.16.02, or any version starting with 10.15.x or earlier)
  3. Verify IFC file handling capability is present
    Check if the IFC translator or IFC import module is available by looking in the application preferences under File > translators or by searching for IFC-related DLLs in the program directory (typically named with 'ifc' in the filename)
    Affected if IFC file support is installed and enabled in the application
  4. Check for recent IFC file activity
    Review recent documents opened or search for .ifc files on the system. Check Windows Jump List or recent files list for IFC file access
    Affected if IFC files have been opened with the affected application, indicating the vulnerable parsing code was exercised

You are affected if Bentley MicroStation or Bentley View is installed with a version lower than 10.16.03 and the application is used to open or parse IFC files.

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 when available. Until then, avoid opening untrusted or unverified IFC files, and disable automatic file opening in the application.

Recommended fix High confidence

MicroStation 10.16.03 or View 10.16.03

  1. Obtain MicroStation 10.16.03 or View 10.16.03 from Bentley's official download portal or update server
  2. Close all running instances of MicroStation or View before upgrading
  3. Run the Bentley installer or update package to upgrade to version 10.16.03
  4. Follow the on-screen prompts to complete the installation
  5. Verify the installed version shows 10.16.03 in the application's About dialog

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

Fix this in Microstation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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