CVE-2022-28309
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 disclose sensitive information 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 3DS files. Crafted data in a 3DS file can trigger a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-16308.
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 · moderate confidenceAn out-of-bounds read vulnerability exists in Bentley View's 3DS file parser. By crafting a malicious 3DS file with data that extends beyond the allocated buffer boundaries, an attacker can read sensitive information from memory. While user interaction is required (opening a malicious file), this vulnerability can be chained with other flaws to achieve arbitrary code execution.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 the installed Bentley productOpen the application and navigate to Help > About, or check the installed programs list in Windows Control Panel to confirm whether Bentley Microstation or Bentley View is installedAffected if The product is Bentley Microstation or Bentley View with a version lower than 10.16.03
-
Determine the exact version numberIn the application, go to Help > About or Help > About Bentley [Product Name] and note the full version string displayed (for example, 10.16.00.XX or earlier)Affected if The installed version is any release prior to 10.16.03
-
Confirm 3DS file parsing is in useCheck if the organization or user workflow involves opening, importing, or rendering .3ds format files within the Bentley applicationAffected if The environment processes or has the capability to process 3DS files from any source
-
Assess file source trust levelReview whether 3DS files originate from trusted internal sources or potentially untrusted external sources, and examine any file handling policies in placeAffected if The environment opens 3DS files from untrusted or unknown sources without verification
A user is affected if they have Bentley Microstation or View installed with a version below 10.16.03 and the application is used to open or process 3DS files, particularly from untrusted sources.
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 the vendor patch when available. Until then, restrict opening of 3DS files from untrusted sources and implement network-level controls to block malicious file delivery.
10.16.03
- Identify the current installed version of Bentley Microstation or Bentley View
- Navigate to the Bentley product download page or use the in-product update checker
- Download Bentley View version 10.16.03 or Microstation version 10.16.03 (or later)
- Close any running instances of the affected Bentley product
- Install the updated version following the standard Bentley installation procedure
- Verify the installed version is 10.16.03 or later by checking About in the product
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28309 — 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-28309 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