CVE-2022-28312
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 disclose sensitive information 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 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-16342.
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 an out-of-bounds read vulnerability in Bentley MicroStation CONNECT's 3DS file parser. Attackers craft malicious 3DS files containing data that causes the parser to read beyond the boundaries of an allocated buffer, leaking sensitive memory contents. Exploitation requires user interaction (opening a malicious 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.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Bentley productOpen the application and go to Help > About MicroStation (or About Bentley View), or check Programs and Features in Windows Control Panel for 'Bentley MicroStation CONNECT' or 'Bentley View'Affected if Either MicroStation CONNECT or Bentley View is installed
-
Determine installed version numberIn the About dialog, note the version number displayed (typically shown as 10.x.x.x). Alternatively, right-click the application in Programs and Features and select Properties to view the versionAffected if Version number is visible and can be compared
-
Compare version against affected rangeCompare your installed version to 10.16.03 - note that versions are considered vulnerable if they are LOWER than 10.16.03 (e.g., 10.16.02, 10.15.00, 10.00.00)Affected if Installed version is below 10.16.03 (any 10.x.x version where the build is less than 1603)
-
Verify 3DS file handling is availableAttempt to open or import a 3DS file through File > Open or File > Import in the Bentley application, or check if 3DS is listed in supported import formatsAffected if 3DS file format can be opened or imported in the application (this is a standard feature in both affected products)
User is affected if Bentley MicroStation CONNECT or Bentley View is installed with a version number lower than 10.16.03 and the application can handle 3DS 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.16.03
Restrict opening of 3DS files from untrusted sources; implement bounds checking in 3DS parsing logic; apply vendor patches when available.
10.16.03 or later
- 1. Identify current Bentley MicroStation or MicroStation View version (Help > About MicroStation)
- 2. Obtain MicroStation version 10.16.03 or later from Bentley (www.bentley.com) or through your Bentley software portal
- 3. Install the updated version following standard Bentley upgrade procedures
- 4. Verify the version has been updated to 10.16.03 or later after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28312 — 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-28312 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