CVE-2021-46633
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 MicroStation CONNECT 10.16.0.80. 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 PDF files. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-15463.
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 · moderate confidenceA use-after-free or similar object validation vulnerability exists in Bentley MicroStation CONNECT's PDF parser. The code fails to validate the existence of an object before performing operations on it, allowing remote attackers to execute arbitrary code via malicious PDF files requiring user interaction.
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.0.80< 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 the installed Bentley product and versionOpen the Bentley application (MicroStation, MicroStation Connect, or View) and check the version information, typically found in the About or Help > About dialog, or by searching for the version in the application's Help menuAffected if The installed version falls below 10.16.02 for MicroStation or View, or is at or below 10.16.0.80 for MicroStation Connect
-
Confirm the product includes PDF parsing capabilityVerify that the installed Bentley product has the ability to open or import PDF files, which is typically available in standard installations of MicroStation, Connect, and ViewAffected if PDF parsing functionality is present in the installation
-
Compare your installed version against affected rangesReview the installed version number against the following affected ranges: Bentley MicroStation versions below 10.16.02, Bentley MicroStation Connect versions 10.16.0.80 and below, and Bentley View versions below 10.16.02Affected if Your installed version matches any of these affected ranges (less than 10.16.02 for MicroStation/View, or less than or equal to 10.16.0.80 for Connect)
You are affected if you are running any version of Bentley MicroStation, MicroStation Connect, or View that falls within the affected version ranges and you have the ability to open PDF files in the application.
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 PDF files and apply vendor-supplied patches when released. Restrict file handling to trusted sources.
MicroStation and View: 10.16.02 or later; MicroStation Connect: version newer than 10.16.0.80 (e.g., 10.16.0.90)
- Identify the exact MicroStation product variant installed (MicroStation, MicroStation Connect, or View)
- Navigate to the Bentley product download page or contact Bentley support to obtain the fixed version
- For MicroStation: upgrade to version 10.16.02 or later
- For MicroStation Connect: upgrade to a version newer than 10.16.0.80 (such as 10.16.0.90 or later if available)
- For View: upgrade to version 10.16.02 or later
- Verify the upgrade was successful by checking the About section in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-46633 — 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-46633 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