CVE-2022-28307
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 DXF files. Crafted data in a DXF file can trigger a read 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-16306.
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 over-read vulnerability in Bentley View's DXF file parser allows attackers to read beyond allocated memory boundaries. By crafting a malicious DXF file that triggers this out-of-bounds read, an attacker can achieve arbitrary code execution within the context of the current user 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.
-
Identify installed Bentley productsCheck for Bentley Microstation or Bentley View installation by looking in common locations: C:\Program Files\Bentley\ or C:\Program Files (x86)\Bentley\, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'Bentley'Affected if Neither Bentley Microstation nor Bentley View is installed
-
Determine installed versionLocate the main executable (MicroStation.exe or BentleyView.exe) in the installation directory, right-click and select Properties, or use PowerShell: (Get-Item 'C:\Program Files\Bentley\MicroStation\MicroStation.exe').VersionInfo.FileVersionAffected if Version cannot be determined or is missing
-
Compare version to affected rangeCompare the found version number against 10.16.03 - note that version formats may appear as 10.16.02.XX or 10.16.00.XX, so ensure the full version string is evaluatedAffected if Installed version is 10.16.03 or higher (not affected); version is below 10.16.03 (potentially affected)
-
Verify DXF import capability existsLaunch the application and attempt to access the File Open dialog, or check for DXF-related DLLs or configuration files in the installation directory (such as Dxf*.dll or import filter files)Affected if DXF file handling capability is present and the version is below 10.16.03
User is affected if Bentley Microstation or View version is below 10.16.03 and the application can open or parse DXF 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
Restrict opening of DXF files from untrusted sources and apply vendor patches when available; consider implementing file validation or sandboxing for DXF import functionality until a fix is deployed.
10.16.03 or later
- 1. Open Microstation or Bentley View application
- 2. Navigate to Help > About to check the current version number
- 3. If version is below 10.16.03, download the updated version (10.16.03 or later) from the Bentley Systems website or your organization's software distribution channel
- 4. Close all Bentley applications before installation
- 5. Run the installer and follow the on-screen prompts to complete the update
- 6. After installation, verify the version by checking Help > About confirms version 10.16.03 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28307 — 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-28307 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