MicrostationApplication · Bentley

CVE-2022-42900

HIGH · 7.8 CVSS v3.1 Published 2022-10-13
Fix available
A fix is available. Upgrade to 10.17.01.19 / 10.17.01.58 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
Bentley MicroStation and MicroStation-based applications may be affected by out-of-bounds read issues when opening crafted FBX files. Exploiting these issues could lead to information disclosure and code execution. The fixed versions are 10.17.01.58* for MicroStation and 10.17.01.19* for Bentley View.

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

Out-of-bounds read vulnerability in Bentley MicroStation and MicroStation-based applications when parsing crafted FBX (Filmbox) 3D model files. This memory safety issue in the FBX file parser can allow attackers to read adjacent memory contents (information disclosure) and potentially achieve code execution through heap manipulation or similar techniques.

MitigationApply vendor patches: update MicroStation to version 10.17.01.58* or later, and Bentley View to 10.17.01.19* or later. Until patched, avoid opening FBX files from untrusted 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.17.01.58
ViewApplication
Affected:< 10.17.01.19

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 installation on the system. Look in Program Files for Bentley folders or check installed programs list.
    Affected if Either MicroStation or Bentley View is installed
  2. Determine installed version of MicroStation
    Locate the MicroStation executable (typically in the Bentley installation folder) and check its version property, or use the application's About dialog to view the version number.
    Affected if The version is below 10.17.01.58
  3. Determine installed version of Bentley View
    Locate the Bentley View executable and check its version property, or use the application's About dialog to view the version number.
    Affected if The version is below 10.17.01.19
  4. Verify FBX file handling capability
    Confirm that the installed Bentley application has FBX import functionality enabled or available. This may be a built-in feature or an optional translator module.
    Affected if FBX parsing capability is present in the installation

A system is affected if it runs MicroStation versions below 10.17.01.58 or Bentley View versions below 10.17.01.19 and has the ability to open or import FBX 3D model 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.17.01.19 / 10.17.01.58 or later
Fixed in 10.17.01.1910.17.01.58
Interim mitigation

Apply vendor patches: update MicroStation to version 10.17.01.58* or later, and Bentley View to 10.17.01.19* or later. Until patched, avoid opening FBX files from untrusted sources.

Recommended fix High confidence

MicroStation 10.17.01.58+ or Bentley View 10.17.01.19+

  1. 1. Identify the installed version of MicroStation or Bentley View by accessing the application's About or Help menu
  2. 2. For MicroStation users: Upgrade to version 10.17.01.58 or later
  3. 3. For Bentley View users: Upgrade to version 10.17.01.19 or later
  4. 4. Verify the upgrade was successful by checking the version number again
  5. 5. Avoid opening untrusted or crafted FBX files until the upgrade is complete

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-42900 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-42900 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