dbcve.org
Bentley ViewApplication · Bentley

CVE-2021-34919

HIGH · 7.8 CVSS v3.1 Published 2022-01-13
Fix available
A fix is available. Upgrade to 10.16.02 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
This 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 JP2 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-14897.

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 confidence

This is a NULL pointer dereference vulnerability in Bentley View's JP2 (JPEG2000) file parser. The code fails to validate that an object exists before performing operations on it, allowing an attacker who tricks a user into opening a malicious JP2 file to achieve code execution in the context of the current process.

MitigationDo not open untrusted JP2 files in Bentley View. Apply vendor patches when available. Consider using application sandboxing or restricted file handling for untrusted content.

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
Bentley ViewApplication
Affected:< 10.16.02
MicrostationApplication
Affected:< 10.16.02

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Bentley View is installed
    Open Windows Control Panel > Programs and Features, or use 'Get-ItemProperty' PowerShell command: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Bentley View*'}
    Affected if Bentley View appears in installed programs list
  2. Check if Microstation is installed
    Open Windows Control Panel > Programs and Features, or use 'Get-ItemProperty' PowerShell command: Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*Microstation*'}
    Affected if Microstation appears in installed programs list
  3. Determine installed version of Bentley View
    Right-click the installed Bentley View entry in Programs and Features and select Properties, or locate the executable (typically in C:\Program Files\Bentley\View\) and check file properties for the version number
    Affected if Version shown is below 10.16.02 (for example, 10.16.00, 10.15.x, etc.)
  4. Determine installed version of Microstation
    Right-click the installed Microstation entry in Programs and Features and select Properties, or locate the executable (typically in C:\Program Files\Bentley\Microstation\) and check file properties for the version number
    Affected if Version shown is below 10.16.02 (for example, 10.16.00, 10.15.x, etc.)
  5. Verify JP2 file handling capability exists
    Confirm that the installed Bentley View or Microstation includes JP2/JPEG2000 image parsing support by checking if the application can open .jp2 files or by examining installed file format handlers
    Affected if The application includes JP2 parsing capability and can process JPEG2000 images

You are affected if either Bentley View or Microstation is installed with a version lower than 10.16.02 and the JP2 file parsing feature is available in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.16.02 or later
Fixed in 10.16.02
Interim mitigation

Do not open untrusted JP2 files in Bentley View. Apply vendor patches when available. Consider using application sandboxing or restricted file handling for untrusted content.

Recommended fix High confidence

Bentley View 10.16.02 or later / Microstation 10.16.02 or later

  1. 1. Obtain the latest version of Bentley View (10.16.02 or later) from the official Bentley website
  2. 2. Alternatively, obtain the latest version of Microstation (10.16.02 or later) if that product is also in use
  3. 3. Download the update from Bentley's support portal or software distribution channel
  4. 4. Close all instances of Bentley View or Microstation
  5. 5. Run the installer and follow the prompts to complete the upgrade
  6. 6. Verify the installed version matches 10.16.02 or higher
  7. 7. Exercise caution when opening JP2 files from untrusted sources

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bentley View Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34919 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-34919 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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