CVE-2022-28301
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. Crafted data in an IFC file can trigger a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16392.
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 confidenceA buffer overflow vulnerability exists in Bentley MicroStation CONNECT when parsing IFC files. The vulnerability occurs during IFC file parsing where crafted data can write past the end of an allocated buffer, allowing an attacker to execute arbitrary code in the context of the current process. User interaction is required, such as opening 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 productCheck Programs and Features or the application's About/Help dialog for the installed product name (Bentley MicroStation CONNECT or Bentley View)Affected if Either Bentley MicroStation or Bentley View is installed on the system
-
Check installed version numberRight-click the installed application executable, select Properties, then view the Details tab for Version info. Alternatively, open the application and go to Help > About to see the exact version numberAffected if The installed version is lower than 10.16.03 (for example, 10.16.00, 10.15.x, or earlier)
-
Determine if IFC file parsing is usedCheck whether users in the environment work with IFC (Industry Foundation Classes) files, which are commonly used in BIM workflows. Search for .ifc file associations or recent IFC file activityAffected if The product processes IFC files and users open or work with IFC files from any source
A user is affected if they have Bentley MicroStation or Bentley View installed with a version lower than 10.16.03 and their workflow involves opening or parsing IFC 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
Apply vendor-supplied patches when available. Until then, restrict opening IFC files from untrusted sources and implement endpoint detection rules for suspicious IFC file handling.
MicroStation 10.16.03 or later / MicroStation View 10.16.03 or later
- Backup your current MicroStation installation and any critical design files
- Download MicroStation version 10.16.03 or later from the official Bentley Systems website (www.bentley.com)
- Run the Bentley installer and select the upgrade/install option
- Follow the on-screen prompts to complete the installation
- After installation, verify the version by checking Help > About MicroStation - it should show 10.16.03 or higher
- Test that IFC files open correctly in the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28301 — 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-28301 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