CVE-2021-46656
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-15631.
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 buffer overflow vulnerability exists in Bentley View 10.15.0.75 when parsing JT files. The parser does not properly validate bounds when processing crafted data within a JT file, allowing a write past the end of an allocated buffer. This can be exploited to achieve arbitrary code execution in the context of the current user 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.
-
Check installed Bentley View versionOpen Bentley View, go to Help > About, or view the program in Windows Add/Remove Programs to determine the exact version numberAffected if The installed version is below 10.16.02 (for example, 10.15.0.75 as noted in the CVE)
-
Check installed Bentley Microstation versionOpen Microstation, go to Help > About, or view the program in Windows Add/Remove Programs to determine the exact version numberAffected if The installed version is below 10.16.02 and the software handles JT files
-
Confirm JT file parsing capabilityAttempt to open a JT file in the installed Bentley software, or check if JT file handlers are registered in the installationAffected if The software can open and parse .jt files, which activates the vulnerable parser code
-
Determine exposure to untrusted JT filesReview whether the software is used to open JT files from external or untrusted sources, or if it processes JT files automaticallyAffected if The software routinely opens JT files from sources that could include crafted malicious files
You are affected if Bentley View or Microstation is installed with a version below 10.16.02 and the software is used to parse JT files, as the vulnerability is triggered during JT file processing.
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 the vendor-supplied security update for Bentley View to the patched version. Until patched, avoid opening JT files from untrusted sources or visiting untrusted websites.
10.16.02 or later
- Obtain Bentley Microstation or View version 10.16.02 or later from the official Bentley website or authorized distribution channel
- Close all running instances of Bentley Microstation or View before upgrading
- Install the updated version (10.16.02 or later) following Bentley's standard installation procedures
- Verify the installation by checking the software version (Help > About)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46656 — 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-46656 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