dbcve.org
MicrostationApplication · Bentley

CVE-2022-28303

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 View 10.16.02.022. 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 SKP files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16280.

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

This is a use-after-free or null pointer dereference vulnerability in Bentley View's SKP file parser. The parser fails to validate object existence before performing operations, allowing remote code execution when a user opens a malicious SKP file.

MitigationDo not open untrusted or unknown SKP files. Apply vendor patches when available. Consider disabling file associations or using application sandboxing to limit exposure.

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. Check if Bentley Microstation is installed
    Look for Bentley Microstation in the installed programs list (Windows: Control Panel > Programs and Features, or check C:\Program Files\Bentley\MicroStation\ or C:\Program Files (x86)\Bentley\MicroStation\)
    Affected if Bentley Microstation is found on the system
  2. Check if Bentley View is installed
    Look for Bentley View in the installed programs list (Windows: Control Panel > Programs and Features, or check C:\Program Files\Bentley\View\ or C:\Program Files (x86)\Bentley\View\)
    Affected if Bentley View is found on the system
  3. Determine the installed version of Bentley Microstation
    Open Microstation, go to Help > About Microstation, or check the version in the program's properties. Compare the version number to 10.16.03
    Affected if Version is lower than 10.16.03
  4. Determine the installed version of Bentley View
    Open Bentley View, go to Help > About Bentley View, or check the version in the program's properties. Compare the version number to 10.16.03
    Affected if Version is lower than 10.16.03

The environment is affected if either Bentley Microstation or Bentley View is installed with a version lower than 10.16.03 and the software can open SKP 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

Do not open untrusted or unknown SKP files. Apply vendor patches when available. Consider disabling file associations or using application sandboxing to limit exposure.

Recommended fix High confidence

10.16.03

  1. 1. Identify the currently installed version of Bentley View or MicroStation by opening the application and navigating to Help > About or checking the program's properties.
  2. 2. Navigate to the official Bentley website (www.bentley.com) or the Bentley Communities support portal to download the version 10.16.03 update.
  3. 3. Download the appropriate installer for your product (Bentley View or MicroStation) matching your system architecture (32-bit or 64-bit).
  4. 4. Close all Bentley applications and any related processes before running the installer.
  5. 5. Run the installer with administrator privileges and follow the on-screen prompts to complete the update.
  6. 6. After installation, verify the new version by checking Help > About to confirm version 10.16.03 is installed.
  7. 7. Avoid opening untrusted or unexpected SKP files from unknown sources to reduce exposure to similar vulnerabilities.

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

Fix this in Microstation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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