CVE-2021-34872
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.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 SKP files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14737.
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 confidenceA use-after-free or null pointer dereference vulnerability exists in Bentley View 10.15.0.75 during SKP file parsing. The software fails to validate object existence before performing operations on it, allowing remote attackers to execute arbitrary code via a malicious SKP file opened by the victim.
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
- 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 softwareCheck program files for Bentley View or Microstation installation directories, or use system inventory tools to list installed softwareAffected if Bentley View or Microstation is present on the system
-
Determine installed version numberOpen Bentley View or Microstation, go to Help > About, or right-click the executable and select Properties > Details to view the versionAffected if Version is earlier than 10.16.02 for either product
-
Verify SKP file handling capabilityCheck if the software can open or import SKP files by attempting to open a sample SKP file or reviewing file association settingsAffected if SKP file handling is enabled or available in the installation
-
Confirm file parsing exposureReview whether users in your environment commonly open or receive SKP files from external sources, or check email gateways/file shares for SKP attachmentsAffected if Users process SKP files from untrusted sources
You are affected if Bentley View or Microstation version is below 10.16.02 and your environment involves opening SKP files, since the vulnerability triggers during SKP file parsing without requiring any specific configuration beyond normal file handling.
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
Do not open untrusted SKP files. Apply vendor-provided patches when released. Implement network-level filtering to block suspicious file attachments.
10.16.02
- 1. Close any running instances of Bentley View or MicroStation
- 2. Navigate to the Bentley product download page or your organization's software distribution system
- 3. Download the version 10.16.02 or later installer for your product (Bentley View or MicroStation)
- 4. Run the installer with appropriate administrative privileges
- 5. Follow the on-screen installation wizard prompts to complete the upgrade
- 6. Restart the application after installation completes
- 7. Verify the installed version by checking Help > About to confirm version 10.16.02 or later is installed
- 8. Avoid opening untrusted SKP files from unknown sources to reduce exposure until patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34872 — 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-34872 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