CVE-2022-40201
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 Systems MicroStation Connect versions 10.17.0.209 and prior are vulnerable to a Stack-Based Buffer Overflow when a malformed design (DGN) file is parsed. This may allow an attacker to execute arbitrary code.
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 confidenceMicroStation Connect versions 10.17.0.209 and prior contain a stack-based buffer overflow vulnerability when parsing malformed DGN design files. An attacker can trigger this vulnerability by convincing a user to open a specially crafted DGN file, potentially leading to arbitrary code execution with the privileges of the running user.
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.0.209CVSS 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.
-
Verify MicroStation Connect installationCheck if Bentley MicroStation Connect is installed on the system. Look for the application in Program Files, Program Files (x86), or use system inventory tools to detect the software.Affected if MicroStation Connect is installed on the system
-
Determine installed versionLocate and read the version information for MicroStation Connect. This can typically be found in the application properties, registry entries under HKLM\SOFTWARE\Bentley\MicroStation, or by running the executable with a version flag if available.Affected if The installed version cannot be determined or is 10.17.0.209 or lower
-
Compare version to affected rangeCompare the identified version number against the affected range: versions 10.17.0.209 and prior are vulnerable. Any version greater than 10.17.0.209 is not affected.Affected if The installed version is 10.17.0.209 or lower (any version up to and including 10.17.0.209)
-
Assess DGN file processing exposureDetermine if users in the environment routinely open DGN design files using MicroStation Connect. Check for recent DGN file access activity or survey users about their workflow.Affected if Users open DGN files from untrusted or external sources using the vulnerable software version
The environment is affected if MicroStation Connect version 10.17.0.209 or lower is installed and users open DGN files with it, as the stack-based buffer overflow can be triggered by malformed DGN 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.
From vendor dataUpdate MicroStation Connect to a version newer than 10.17.0.209. Until patched, avoid opening DGN files from untrusted sources.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.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 $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-40201 — 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-40201 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