CVE-2022-28306
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 execute arbitrary code 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 OBJ files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this to execute code in the context of the current process. Was ZDI-CAN-16174.
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 confidenceStack-based buffer overflow in Bentley MicroStation CONNECT's OBJ file parser. The parser fails to validate the length of user-supplied data before copying it into a fixed-length stack buffer, allowing remote code execution via a specially crafted OBJ file that requires user interaction (opening the file or visiting a malicious page).
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
- 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 installed programs list in Windows Control Panel > Programs and Features, or use 'wmic product get name,version' command. Look for either 'Bentley MicroStation CONNECT' or 'Bentley View'.Affected if The installed product is MicroStation CONNECT or Bentley View with version less than 10.16.03
-
Confirm exact version numberOpen MicroStation or Bentley View, go to Help > About, or right-click the application executable and view Properties > Details to see the precise version string.Affected if The version shown is below 10.16.03 (for example, 10.16.00, 10.15.x, or earlier)
-
Verify OBJ file import capabilityAttempt to use the File > Open or File > Import dialog and filter for .obj files, or check the application help documentation for OBJ import support.Affected if The application can import or open OBJ files and the version is below 10.16.03
-
Check for recent OBJ file processingReview recent files lists within the application (File > Recent), Windows Jump Lists, or system activity logs for any recently opened .obj files from untrusted sources.Affected if Untrusted OBJ files have been opened and the installed version is vulnerable
You are affected if you have MicroStation CONNECT or Bentley View installed with any version lower than 10.16.03.
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 vendor patch when released; until then, enforce user awareness to avoid opening untrusted OBJ files and consider application whitelisting as compensating control.
10.16.03
- Obtain MicroStation CONNECT version 10.16.03 from Bentley's official website or authorized distribution channels
- Back up any critical projects, files, and user settings before upgrading
- Uninstall the current affected version (e.g., 10.16.02.034) or use Bentley's update mechanism
- Install version 10.16.03 following Bentley's standard installation procedures
- Launch the application and verify the installation was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28306 — 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-28306 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