CVE-2021-46642
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.15.0.75. 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 DGN files. The issue results from the lack of proper validation of user-supplied data, which can result in 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-15514.
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 out-of-bounds read vulnerability in Bentley View when parsing DGN files. The lack of proper validation of user-supplied data during DGN parsing allows an attacker to read past the end of an allocated buffer, exposing sensitive information. This vulnerability can be chained with other vulnerabilities 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.02< 10.16.02CVSS 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.
-
Verify Bentley software is installedCheck system for installed Bentley Microstation or Bentley View applications. Look in Program Files for 'Bentley' folder, or use system inventory tools to detect Bentley applications.Affected if Bentley Microstation or Bentley View is present on the system
-
Determine installed version of Bentley MicrostationOpen Microstation, go to Help > About Microstation, or check the program's file properties (right-click executable > Properties > Details). The version is typically displayed there.Affected if Version is lower than 10.16.02
-
Determine installed version of Bentley ViewOpen Bentley View, go to Help > About Bentley View, or check the program's file properties. The version is typically displayed there.Affected if Version is lower than 10.16.02
-
Confirm DGN file handling is enabledVerify that the application can parse DGN files. This is a core file format capability in Microstation and View - check if DGN import/open functionality is available in the application.Affected if DGN file parsing capability is present in the installed software
If Bentley Microstation or Bentley View is installed with a version lower than 10.16.02 and DGN file parsing is enabled, the environment is affected by this vulnerability.
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.02
Avoid opening untrusted or malicious DGN files in Bentley View. Apply vendor patches when available from Bentley Systems.
10.16.02 or later
- 1. Identify the installed Bentley product (MicroStation or Bentley View) and current version by opening the application and checking Help > About
- 2. Navigate to the official Bentley support website (www.bentley.com) and locate the downloads section for your product
- 3. Download version 10.16.02 or later of the affected product
- 4. Close all Bentley applications and any related processes
- 5. Run the installer and follow the on-screen prompts to apply the update
- 6. Restart the application after installation completes
- 7. Verify the version has been updated to 10.16.02 or later by checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46642 — 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-2021-46642 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