CVE-2021-46615
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 disclose sensitive information 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 BMP images. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-15409.
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 confidenceAn out-of-bounds read vulnerability in the BMP image parser of Bentley MicroStation CONNECT 10.16.0.80 allows remote attackers to read past the end of an allocated buffer due to lack of proper validation of user-supplied data. Successful exploitation enables information disclosure; chaining with other vulnerabilities could lead to arbitrary code execution.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 product versionOpen the application and go to Help > About Bentley MicroStation or About Bentley View, or check the program's properties in Windows Explorer. Alternatively, run 'msiexec' or check Add/Remove Programs for the exact version number.Affected if The version is Bentley Microstation < 10.16.02, Microstation Connect <= 10.16.0.80, or Bentley View < 10.16.02
-
Verify the BMP parsing module is presentBMP image support is a built-in feature of MicroStation's raster manager. Check if the application's raster or image import capabilities are functional by attempting to view any image file or checking the application's installed components.Affected if The application has raster/image viewing capabilities enabled (this is typically enabled by default in standard installations)
-
Identify recent BMP file processing activityCheck Windows Event Viewer for recent file operations, or examine recent document locations and TEMP folders for .bmp files that may have been opened. Also check browser download histories if web browsing occurred within the application.Affected if Users have recently opened BMP files from untrusted or unknown sources, or the application has processed BMP files from external websites
You are affected if your installed version falls within the affected ranges (Microstation < 10.16.02, Microstation Connect <= 10.16.0.80, or View < 10.16.02) and you have opened or processed BMP files in the vulnerable 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
Apply vendor patches when available. Until then, enforce user awareness to avoid opening untrusted BMP files or visiting suspicious websites.
MicroStation 10.16.02 or later; MicroStation Connect 10.16.0.81 or later
- 1. Identify the currently installed Bentley MicroStation version (Microstation, MicroStation Connect, or View)
- 2. Navigate to the Bentley product download portal or check for updates within the application
- 3. Download and install MicroStation version 10.16.02 or later for Microstation and View users
- 4. For MicroStation Connect users, download and install version 10.16.0.81 or later
- 5. Verify the installed version matches or exceeds the fixed release number
- 6. Restart the application after upgrading
- 7. Test BMP file parsing functionality to ensure normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2021-46615 — 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-46615 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