CVE-2022-42901
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 and stack overflow issues when opening crafted XMT 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/write and stack overflow vulnerabilities when parsing specially crafted XMT files. An attacker can exploit these file parsing flaws to achieve information disclosure and potentially execute arbitrary code via a malicious XMT file.
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.
-
Identify installed Bentley productCheck the application name in the system menu or Add/Remove Programs. Look for either 'Bentley MicroStation' or 'Bentley View'.Affected if The system has MicroStation or Bentley View installed.
-
Find the installed version numberOpen the installed application, go to Help > About, or right-click the executable and select Properties > Details to view the version number.Affected if A version number is displayed in the format such as 10.XX.XX.XX.
-
Compare version to affected rangesFor MicroStation, compare the installed version to 10.17.01.58 (vulnerable if below this). For Bentley View, compare to 10.17.01.19 (vulnerable if below this).Affected if MicroStation version is below 10.17.01.58 OR Bentley View version is below 10.17.01.19.
-
Assess XMT file exposureDetermine if the software can open or parse XMT files. Check if XMT is a native or supported file format for the installed product.Affected if The software can load or preview XMT files as a normal feature.
If the installed MicroStation is below version 10.17.01.58 or Bentley View is below 10.17.01.19, and the software can process XMT files, the environment is vulnerable to this CVE.
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, avoid opening XMT files from untrusted sources.
MicroStation 10.17.01.58 or Bentley View 10.17.01.19
- Identify whether you are running MicroStation or Bentley View (or a MicroStation-based application)
- Determine the current installed version of the software
- If running MicroStation and version is below 10.17.01.58, upgrade to version 10.17.01.58 or later
- If running Bentley View and version is below 10.17.01.19, upgrade to version 10.17.01.19 or later
- Verify the upgrade was successful by checking the updated version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42901 — 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-42901 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