CVE-2022-28313
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-16343.
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. A malicious 3DS file with crafted data can trigger a read past the end of an allocated buffer, allowing remote attackers to disclose sensitive information from memory. User interaction is required (opening the file), and this flaw can be chained with other vulnerabilities for 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.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 the installed Bentley productCheck Programs and Features (Windows) or the application's About dialog for the product name - either MicroStation CONNECT or Bentley ViewAffected if The product is Bentley MicroStation CONNECT or Bentley View
-
Determine the installed version numberOpen the application, go to Help > About Bentley [Product Name], or check the version in the application's main window. The version is typically displayed as 10.x.x.xAffected if The version number is lower than 10.16.03 (e.g., 10.16.00, 10.15.x, 10.14.x, etc.)
-
Confirm 3DS file handling capability existsVerify the application can open or import 3DS files by checking File > Open or File > Import for .3ds file type support, or attempt to open a known 3DS fileAffected if The 3DS file import/open functionality is present and accessible in the installed version
-
Verify the vulnerability windowCross-reference the specific build number with Bentley's security advisory if available, noting that any version below 10.16.03 is considered vulnerableAffected if The installed version is 10.16.02, 10.16.01, 10.16.00, or any earlier minor version
You are affected if Bentley MicroStation CONNECT or Bentley View is installed with any version below 10.16.03 and the 3DS file import feature is available to users.
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 from Bentley for MicroStation CONNECT. Until patched, instruct users to avoid opening 3DS files from untrusted sources.
Bentley MicroStation CONNECT 10.16.03 or later / Bentley View 10.16.03 or later
- Navigate to the Bentley product support website or your organization's software distribution center
- Locate Bentley MicroStation CONNECT or Bentley View version 10.16.03 or later
- Download the installer for version 10.16.03
- Close any running instances of MicroStation or View
- Run the installer and follow the prompts to upgrade
- Restart the application after installation completes
- Verify the installed version is 10.16.03 or later by checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28313 — 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-28313 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