CVE-2021-34929
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-14907.
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 10.15.0.75 when parsing maliciously crafted JT (Jupiter Tessellation) files. The parsing logic writes data past the end of an allocated buffer, allowing arbitrary code execution in the context of the current user process. Requires user to open 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 installed programs for Bentley View or Microstation using system inventory tools, registry queries, or program directoriesAffected if Neither Bentley View nor Microstation is installed, the system is not affected by this CVE
-
Determine installed version of Bentley ViewLocate the Bentley View executable (typically in Program Files/Bentley) and query its version property, or check Add/Remove Programs for the installed version numberAffected if Installed version is 10.15.0.75 or any version prior to 10.16.02
-
Determine installed version of MicrostationLocate the Microstation executable and query its version property, or check Add/Remove Programs for the installed version numberAffected if Installed version is prior to 10.16.02 and the product is present
-
Verify JT file handling capabilityConfirm that the installed Bentley product has JT file parsing enabled or available - check file association settings or product configuration for JT file supportAffected if JT file handling is enabled and the version is below 10.16.02
The environment is affected only if Bentley View or Microstation is installed with a version lower than 10.16.02 and JT file parsing capability is present.
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
Apply vendor patch from Bentley when available. Until then, restrict opening JT files from untrusted sources and deploy endpoint detection/response controls to monitor for exploitation attempts.
Bentley View 10.16.02 or later / Microstation 10.16.02 or later
- 1. Identify all affected Bentley View and/or Microstation installations in your environment
- 2. Verify the current version of each installation (help > about or file > properties)
- 3. Download Bentley View version 10.16.02 or later from the official Bentley website (www.bentley.com)
- 4. Download Microstation version 10.16.02 or later from the official Bentley website (www.bentley.com)
- 5. Ensure all users close any running instances of Bentley View or Microstation
- 6. Install the updated version of the affected product(s) on all impacted systems
- 7. Apply the update following standard Bentley software deployment procedures
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34929 — 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-34929 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