CVE-2022-28320
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 View 10.16.02.022. 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 3DM files. The issue results from the lack of proper initialization of memory prior to accessing it. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-16282.
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 uninitialized memory vulnerability in Bentley View's 3DM file parser. The lack of proper initialization of memory prior to accessing it allows attackers to execute arbitrary code by enticing users to open malicious 3DM files, achieving code execution in the context of the current process.
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.
-
Verify Bentley software is installedCheck Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Bentley Microstation' or 'Bentley View', or use 'Get-ItemProperty' PowerShell command against common installation directories like C:\Program Files\BentleyAffected if neither Bentley Microstation nor Bentley View is found on the system, the vulnerability does not apply
-
Identify the exact product name and versionFor each found Bentley product, retrieve the DisplayVersion value from the registry or check the version info of the main executable (such as BentleyView.exe or MicroStation.exe) using 'Get-ItemProperty' or right-click Properties in File ExplorerAffected if the product name is not Bentley Microstation or Bentley View, or version cannot be determined
-
Compare installed version against affected rangeCompare the installed version number to 10.16.03 using standard version comparison (for example, 10.16.00, 10.15.02, or 10.00.00 would all be less than 10.16.03)Affected if the installed version is 10.16.03 or higher, the vulnerability does not apply; if the version is less than 10.16.03 or cannot be determined, the system may be affected
-
Confirm 3DM file handling capabilitySearch for .3dm file associations or check if the software has been used to open 3DM files by reviewing recent documents or MRU (Most Recently Used) lists in the applicationAffected if 3DM files have never been opened or the file type is not associated with the installed software, the practical risk is reduced though the code vulnerability still exists in the parser
The environment is affected if Bentley Microstation or Bentley View is installed with a version lower than 10.16.03, regardless of whether 3DM files have actually been processed.
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 for Bentley View. Until patched, advise users to avoid opening 3DM files from untrusted sources.
10.16.03
- 1. Ensure all work is saved and closed in MicroStation or Bentley View
- 2. Navigate to the Bentley product support page at www.bentley.com or use the in-product update checker
- 3. Download Bentley View version 10.16.03 or later (or MicroStation version 10.16.03 or later if using that product)
- 4. Run the installer with administrative privileges
- 5. Follow the on-screen installation prompts to complete the upgrade
- 6. Restart the application after installation completes
- 7. Verify the version by checking Help > About to confirm version 10.16.03 or higher is installed
- 8. Avoid opening untrusted 3DM files from unknown sources until the update is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28320 — 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-28320 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