CVE-2021-34935
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 JT files. Crafted data in a JT file can trigger a write 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-14913.
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 confidenceBuffer overflow vulnerability in Bentley View's JT file parser. When parsing a maliciously crafted JT file, the application writes data past the end of an allocated buffer, allowing arbitrary code execution in the context of the current process. Requires user to open the malicious file.
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 if Bentley View is installedCheck for Bentley View installation by looking in program files directories (C:\Program Files\Bentley\Bentley View or C:\Program Files (x86)\Bentley\Bentley View) or use system inventory toolsAffected if Bentley View is found on the system
-
Identify if Microstation is installedCheck for Microstation installation by looking in program files directories (C:\Program Files\Bentley\MicroStation or C:\Program Files (x86)\Bentley\MicroStation) or use system inventory toolsAffected if Microstation is found on the system
-
Determine installed version of Bentley ViewRight-click the Bentley View executable (BentleyView.exe) in the installation directory, select Properties, and check the Details tab for version information, or run: dir "C:\Program Files\Bentley\Bentley View\BentleyView.exe"Affected if Version is found to be below 10.16.02
-
Determine installed version of MicrostationRight-click the MicroStation executable (MicroStation.exe orustn.exe) in the installation directory, select Properties, and check the Details tab for version information, or run: dir "C:\Program Files\Bentley\MicroStation\MicroStation.exe"Affected if Version is found to be below 10.16.02
User is affected if either Bentley View or Microstation is installed with a version lower than 10.16.02 and the application can be used to open JT files 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.02
Avoid opening untrusted JT files from unknown sources. Apply vendor patches or update to the latest Bentley View version when available.
10.16.02 or later
- 1. Identify whether you are using Bentley View or Microstation
- 2. Check the current installed version (Help > About)
- 3. Navigate to the Bentley software downloads page or use the in-product update checker
- 4. Download Bentley View version 10.16.02 or later, OR Microstation version 10.16.02 or later
- 5. Close all instances of the application
- 6. Run the installer and follow the prompts to complete the update
- 7. Verify the update was successful by checking the version number in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34935 — 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-34935 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