CVE-2021-34925
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. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14903.
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 confidenceA stack-based buffer overflow vulnerability exists in Bentley View 10.15.0.75 during JT file parsing. The vulnerability results from insufficient validation of user-supplied data length before copying to a stack-based buffer, allowing remote code execution in the current process context when a user opens a malicious JT 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 installed Bentley productCheck if Bentley View or Microstation is installed by looking for the application in Program Files/Bentley or checking the Windows uninstall listAffected if Either Bentley View or Microstation is installed
-
Check Bentley View versionRight-click the Bentley View executable (usually in C:\Program Files\Bentley\View\ or similar), select Properties, and view the File Version under the Details tabAffected if The version shown is lower than 10.16.02 (e.g., 10.15.0.75 or any 10.x.x.x version below 10.16.02)
-
Check Microstation versionRight-click the Microstation executable (usually in C:\Program Files\Bentley\Microstation\ or similar), select Properties, and view the File Version under the Details tabAffected if The version shown is lower than 10.16.02 (e.g., any 10.x.x.x version below 10.16.02)
-
Verify JT file handling capabilityAttempt to open a JT file in the installed application or check if JT file association exists in Windows (look for .jt file type associated with Bentley View or Microstation)Affected if The application can open or is associated with .jt files and the version is below 10.16.02
You are affected if either Bentley View or Microstation is installed with a version lower than 10.16.02 and the application can process JT 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 or unverified JT files in Bentley View. Apply vendor patches when released. Consider network segmentation to limit exposure to remote attack vectors.
10.16.02
- Identify the current installed version of Bentley View or MicroStation
- Download version 10.16.02 or later from the official Bentley website (www.bentley.com)
- Close any running instances of Bentley View or MicroStation
- Run the installer to apply the update
- Verify the installed version is 10.16.02 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34925 — 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-34925 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