CVE-2022-28310
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 · uneditedThis 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 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-16339.
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 confidenceThis is a memory corruption vulnerability in Bentley MicroStation CONNECT where the SKP file parser fails to validate object existence before performing operations on it, leading to potential arbitrary code execution in the context of the current process.
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< 10.16.03< 10.16.03CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bentley productCheck Program Files for 'Bentley MicroStation CONNECT' or 'Bentley View' folder, or check Windows Programs and Features for installed Bentley softwareAffected if Either MicroStation CONNECT or Bentley View is installed
-
Determine installed version of MicroStationOpen MicroStation, go to Help > About MicroStation, or right-click the executable in Program Files and view Properties > Details for version infoAffected if Version shown is below 10.16.03 (e.g., 10.16.00, 10.15.x, etc.)
-
Determine installed version of Bentley ViewOpen Bentley View, go to Help > About Bentley View, or check the executable properties in Program Files for version informationAffected if Version shown is below 10.16.03 (e.g., 10.16.00, 10.15.x, etc.)
-
Check if SKP file handling is accessibleAttempt to open any .SKP file in the application, or verify the SKP import/load capability is available in the productAffected if The product can load SKP files and the installed version is below 10.16.03
You are affected if Bentley MicroStation CONNECT or Bentley View is installed with a version number lower than 10.16.03, as the vulnerable SKP file parser is present in those versions.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.16.03
Apply the vendor patch when available; until then, restrict opening untrusted SKP files and educate users about the risks of opening files from unknown sources.
MicroStation and MicroStation View 10.16.03
- 1. Close all running instances of Bentley MicroStation or MicroStation View
- 2. Navigate to the official Bentley Systems support portal or software download page
- 3. Locate and download MicroStation CONNECT version 10.16.03 or later
- 4. Run the installer with appropriate administrative privileges
- 5. Follow the on-screen installation prompts to complete the upgrade
- 6. Verify the installed version by checking Help > About MicroStation to confirm version 10.16.03 or higher
- 7. Test that SKP file parsing works correctly with the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28310 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-28310 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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