CVE-2022-42899
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 · uneditedBentley MicroStation and MicroStation-based applications may be affected by out-of-bounds read and stack overflow issues when opening crafted SKP 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 confidenceBentley MicroStation and MicroStation-based applications contain out-of-bounds read and stack overflow vulnerabilities when parsing crafted SKP (SketchUp) files. An attacker can exploit these by tricking a user into opening a malicious SKP file, potentially leading to information disclosure and arbitrary code 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< 10.17.01.58< 10.17.01.19CVSS 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.
-
Check installed MicroStation versionOpen MicroStation, then go to Help > About Bentley MicroStation to view the version number. Alternatively, locate the MicroStation executable file, right-click, select Properties, and check the Details tab for the product version.Affected if The version is lower than 10.17.01.58
-
Check installed Bentley View versionOpen Bentley View, then go to Help > About Bentley View to view the version number. Alternatively, locate the Bentley View executable file, right-click, select Properties, and check the Details tab for the product version.Affected if The version is lower than 10.17.01.19
-
Determine if SKP file support is enabledIn MicroStation or Bentley View, go to File > Open and look for SKP (SketchUp) files in the file type dropdown. Alternatively, check the CAD standards or workspace configuration settings for SketchUp or SKP import/load functionality.Affected if SKP file support is available and users can open SKP files from the file open dialog
-
Check for recent SKP file activityReview recent document history, recent files lists, or Windows Jump Lists for any recently opened .SKP files within the application.Affected if Users have opened SKP files in the affected application version
-
Verify file type associationsCheck if .SKP files are associated with MicroStation or Bentley View by looking at Windows Default Apps settings or checking the Windows registry under HKEY_CLASSES_ROOT for .SKP file associations.Affected if The application is configured as a handler for .SKP files
The user is affected if they have MicroStation version below 10.17.01.58 or Bentley View version below 10.17.01.19, and the application has the ability to open or parse SKP files.
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.17.01.1910.17.01.58
Update MicroStation to version 10.17.01.58 or later, and Bentley View to version 10.17.01.19 or later. Until patched, exercise caution when opening SKP files from untrusted sources.
MicroStation: 10.17.01.58+ | Bentley View: 10.17.01.19+
- Identify the currently installed version of MicroStation or Bentley View
- Navigate to the official Bentley website (www.bentley.com) to obtain the fixed version
- For MicroStation: download version 10.17.01.58 or later
- For Bentley View: download version 10.17.01.19 or later
- Install the updated version following Bentley's standard installation procedures
- Verify the installation by checking the updated version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42899 — 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-42899 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