CVE-2021-34874
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 processing of 3DS files. The issue results from the lack of proper validation of user-supplied data, which can result in a memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14736.
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 confidenceMemory corruption vulnerability in Bentley View 10.15.0.75 when parsing 3DS files. The lack of proper validation of user-supplied data during 3DS file processing allows an attacker to trigger memory corruption and achieve remote 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.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 productCheck for Bentley View or Microstation installation by looking in Program Files for 'Bentley' folder or checking Add/Remove Programs. Common paths: C:\Program Files\Bentley\ or C:\Program Files (x86)\Bentley\Affected if Either Bentley View or Microstation is installed on the system
-
Determine installed versionOpen the Bentley application, go to Help > About, or check the executable properties (right-click on the .exe file and view Version info). The version is displayed as a four-part number like X.X.X.XAffected if Version is less than 10.16.02 (any version starting with 10.15.x or earlier, or 10.16.0 or 10.16.01)
-
Verify 3DS file handling capabilityCheck if the application has 3DS import/export capabilities enabled. In Microstation go to File > Import or check the translators/import settings. In Bentley View, check if 3DS is listed in supported file types under File > OpenAffected if 3DS file import capability is present and enabled in the application
-
Check for recent 3DS file activityReview application log files (typically in %APPDATA%\Bentley\Logs\ or within the project folder) for entries containing '.3ds' or '3DS' file operations. Also check Windows Event Viewer Application logs for Bentley process activityAffected if Any 3DS files have been opened, imported, or processed by the vulnerable application version
The environment is affected if either Bentley View or Microstation version is below 10.16.02 AND the 3DS file parsing feature is available and has been used to process 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.02
Avoid opening untrusted 3DS files and monitor for vendor patches. Restrict file handling to trusted sources only until an update is applied.
10.16.02
- 1. Identify the affected Bentley product (Bentley View or MicroStation) currently installed
- 2. Obtain the fixed version 10.16.02 or later from the official Bentley download portal at www.bentley.com
- 3. Uninstall the current vulnerable version following standard uninstallation procedures
- 4. Install version 10.16.02 or the latest stable release available
- 5. Verify the installation was successful and the product launches without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34874 — 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-34874 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