dbcve.org
MicrostationApplication · Bentley

CVE-2022-28308

MEDIUM · 5.5 CVSS v3.1 Published 2023-03-29
Fix available
A fix is available. Upgrade to 10.16.03 or later.
See remediation →
58/100
Remediation priority · Elevated
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 disclose sensitive information 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 3DS files. Crafted data in a 3DS file can trigger a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-16307.

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

An out-of-bounds read vulnerability exists in Bentley View 10.16.02.022 when parsing 3DS files. The specific flaw allows reading past the end of an allocated buffer during 3DS file parsing, leading to sensitive information disclosure. This vulnerability requires user interaction (opening a malicious 3DS file) and can be chained with other vulnerabilities for arbitrary code execution.

MitigationUpdate Bentley View to the latest patched version when available. Until a patch is released, avoid opening untrusted or unverified 3DS files, and implement application whitelisting to restrict file execution.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 products
    Check for Bentley View or Bentley MicroStation installations in Program Files (typically C:\Program Files\Bentley\View\ or C:\Program Files\Bentley\MicroStation\) or via Windows Add/Remove Programs
    Affected if Either Bentley View or Bentley MicroStation is installed
  2. Determine installed version of Bentley View
    Right-click the Bentley View executable (typically View.exe or similar) in the installation folder, select Properties, and check the Details tab for the Product Version
    Affected if Version is listed as below 10.16.03 or the version field is empty/unknown and the product is Bentley View
  3. Determine installed version of Bentley MicroStation
    Right-click the MicroStation executable (typically MicroStation.exe or similar) in the installation folder, select Properties, and check the Details tab for the Product Version
    Affected if Version is listed as below 10.16.03 or the version field is empty/unknown and the product is Bentley MicroStation
  4. Verify if 3DS file handling is possible
    Attempt to open a 3DS file in the installed Bentley product or check file association settings for .3ds extension
    Affected if The product can open or is associated with .3ds files and version is below 10.16.03

You are affected if you have Bentley View or Bentley MicroStation installed with a version lower than 10.16.03 and you or users in your environment open 3DS files with this software.

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

Update Bentley View to the latest patched version when available. Until a patch is released, avoid opening untrusted or unverified 3DS files, and implement application whitelisting to restrict file execution.

Recommended fix High confidence

10.16.03

  1. 1. Back up any existing project files and user settings before proceeding with the upgrade
  2. 2. Download Bentley View version 10.16.03 (or later) from the official Bentley website at www.bentley.com
  3. 3. Close any running instances of Bentley View or MicroStation
  4. 4. Uninstall the current vulnerable version through the system's Add/Remove Programs or Apps & Features
  5. 5. Run the installer for version 10.16.03 with administrator privileges
  6. 6. Follow the on-screen installation prompts to complete the installation
  7. 7. After installation, verify the version by checking Help > About Bentley View to confirm version 10.16.03 or later is installed
  8. 8. Re-apply any custom settings or restore project files from the backup
Caveat No documented breaking changes identified from the available information; however, users should verify compatibility with custom configurations or third-party integrations

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