dbcve.org
MicrostationApplication · Bentley

CVE-2022-28305

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.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 OBJ files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16172.

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

Stack-based buffer overflow in Bentley MicroStation CONNECT when parsing OBJ files. The application fails to validate the length of user-supplied data before copying it to a fixed-size stack buffer, allowing remote code execution via malicious OBJ files.

MitigationDo not open untrusted or unverified OBJ files. Apply vendor patches when available. Restrict file handling to trusted 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 by looking in the installed programs list or program files directory for Bentley applications.
    Affected if Neither MicroStation nor View is installed, then the system is not affected by this CVE.
  2. Check the installed version number
    Locate the installed Bentley application and check its version. This is typically found in the application's About menu, or by right-clicking the executable in the installation directory and viewing Properties > Details. Compare the version to 10.16.03.
    Affected if The installed version is lower than 10.16.03 for either MicroStation or View, the system falls within the affected version range.
  3. Verify OBJ file import capability
    Determine if the application has the ability to import or open OBJ format files. This is typically available through the File > Import or File > Open dialogs, or by checking file association settings for .obj files.
    Affected if OBJ file import is available and the application can open external OBJ files, the exploitation condition is present.
  4. Assess file handling exposure
    Evaluate whether the system processes OBJ files from external or untrusted sources. Check if users can import OBJ files into the application or if automated processes handle OBJ files.
    Affected if Users or automated systems can open OBJ files from untrusted or unknown sources, the system is exposed to the attack vector described in this CVE.

A system is affected if it has Bentley MicroStation or View installed with a version lower than 10.16.03 and can open or import OBJ files from potentially untrusted 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

Do not open untrusted or unverified OBJ files. Apply vendor patches when available. Restrict file handling to trusted sources.

Recommended fix High confidence

MicroStation CONNECT 10.16.03 or later

  1. 1. Open MicroStation CONNECT and navigate to Help > About MicroStation to verify the current installed version.
  2. 2. If the version is below 10.16.03, download MicroStation CONNECT version 10.16.03 or later from the official Bentley website (www.bentley.com).
  3. 3. Close all MicroStation applications and any Bentley-related processes.
  4. 4. Run the installer with administrative privileges and follow the on-screen prompts to upgrade.
  5. 5. After installation completes, restart your computer if prompted.
  6. 6. Verify the upgrade was successful by checking Help > About MicroStation confirms version 10.16.03 or later.
Caveat Review Bentley's release notes for version 10.16.03 to check for any configuration or workflow changes that may affect existing projects

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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