CVE-2022-28315
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.34. 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 IFC 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 vulnerability to execute code in the context of the current process. Was ZDI-CAN-16367.
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 vulnerability in Bentley MicroStation CONNECT's IFC file parser. The application fails to validate the length of user-supplied data before copying it to a fixed-size stack buffer, allowing remote code execution when a user opens a malicious IFC 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
- 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 product and versionCheck the installed version of Bentley MicroStation CONNECT or Bentley View through the application's About dialog, or through system Add/Remove Programs (Windows) or installed packages listingAffected if The installed product is Bentley MicroStation CONNECT or Bentley View with version below 10.16.03
-
Verify IFC parser functionality is presentCheck if the IFC import/export module is loaded or available in the application's configuration or modules listAffected if IFC file parsing capability exists in the installation
-
Confirm recent IFC file activityReview application logs, recent files list, or document history to determine if IFC files have been openedAffected if IFC files have been opened in the application
A user is affected if they have Bentley MicroStation CONNECT or Bentley View installed with version below 10.16.03 and the IFC file handling functionality is enabled or has been used
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
Do not open IFC files from untrusted sources. Apply vendor patches when released. Consider file sandboxing or endpoint protection as compensating controls.
10.16.03
- 1. Ensure all users close any running instances of MicroStation or View
- 2. Back up any critical project files as a precautionary measure
- 3. Download MicroStation version 10.16.03 or later from the official Bentley website or your Bentley product subscription portal
- 4. Run the installer and follow the on-screen prompts to complete the upgrade
- 5. Verify the installation by launching the application and checking the version number (Help > About)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation10.0 h
- Implementation8.0 h
- Testing10.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 $9,056.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28315 — 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-28315 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