CVE-2021-46631
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 TIF images. The issue results from the lack of proper initialization of memory prior to accessing it. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15461.
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 initialization vulnerability in Bentley View 10.15.0.75's TIF image parser. Remote attackers can execute arbitrary code by tricking users into opening specially crafted malicious TIF files. The flaw stems from improper memory initialization before access during TIF parsing.
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 Microstation or Bentley View installation in system programs, or look for Bentley application executables (such as Microstation.exe or BentleyView.exe) in typical installation directories like C:\Program Files\Bentley\Affected if Either Bentley Microstation or Bentley View is installed on the system
-
Determine installed versionOpen the Bentley application, then navigate to Help > About or use the application's version information dialog. Alternatively, check the executable file properties of the main application binary.Affected if The displayed version is lower than 10.16.02
-
Verify vulnerability windowCompare your installed version number against the affected range (anything below 10.16.02)Affected if Installed version is 10.15.0.75 or any version lower than 10.16.02 for either Microstation or View
-
Confirm TIF file handling is possibleThe vulnerability is triggered when parsing malicious TIF image files - verify the application can open or import TIF filesAffected if TIF file parsing capability exists in the installed product version
A system is affected if either Bentley Microstation or Bentley View is installed with a version lower than 10.16.02 and the application can process TIF image 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
Apply vendor-supplied patch for Bentley View. Until patched, instruct users not to open untrusted TIF files from unknown sources.
10.16.02
- 1. Check current Bentley Microstation or View version via Help > About
- 2. Navigate to the Bentley website or official download portal to obtain version 10.16.02 or later
- 3. Download the installer for the fixed version
- 4. Close any running Bentley applications
- 5. Run the installer and follow the on-screen prompts to upgrade
- 6. After installation, verify the version shows 10.16.02 or higher via Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46631 — 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-46631 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