CVE-2021-34871
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 BMP files. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-14695.
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 confidenceHeap-based buffer overflow in Bentley View's BMP file parser. The application fails to validate the length of user-supplied data before copying it to a heap buffer during BMP parsing, allowing remote code execution in the context of the current 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.
-
Identify if Bentley View or Microstation is installedCheck for Bentley View or Microstation in the list of installed programs on the system (Windows: Programs and Features, Linux: package manager, or search for bentley or microstation in program directories)Affected if Either Bentley View or Microstation is present on the system
-
Determine the installed version of Bentley View or MicrostationOpen the application, go to Help > About, or check the program's properties in the installation directory to find the exact version numberAffected if The version is lower than 10.16.02 (for example, 10.15.x, 10.14.x, or earlier)
-
Confirm BMP file handling capability is presentAttempt to open a BMP file in the application or check if BMP is listed as a supported image format in the application's file open dialog filterAffected if BMP files can be opened or previewed in the application
-
Check if the system processes BMP files from untrusted or external sourcesReview workflows where the application may automatically or manually open BMP files from email attachments, downloaded files, network shares, or user-provided contentAffected if Users can open BMP files from untrusted or unknown sources using the affected application
The system is affected if either Bentley View or Microstation is installed with a version lower than 10.16.02 and the application can be used to open BMP 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
Update to the latest Bentley View version or apply vendor-provided patches. Until then, avoid opening untrusted BMP files from unknown sources.
10.16.02
- Obtain the latest version of Bentley View or Microstation from the official Bentley website or your organization's software distribution channel
- Ensure all users close any running instances of Bentley View or Microstation before proceeding
- Download the installer for version 10.16.02 or later from Bentley's support portal
- Run the installer with appropriate administrative privileges
- Follow the on-screen installation prompts to complete the upgrade
- After installation, verify the version by checking Help > About in the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-34871 — 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-34871 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