CVE-2022-43653
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 · uneditedBentley View SKP File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Bentley View. 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 SKP files. Crafted data in an SKP file can trigger a write past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-19084.
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 write vulnerability exists in Bentley View's SKP file parser. When parsing specially crafted SKP files, the application writes data beyond the bounds of an allocated buffer due to insufficient bounds checking, which can be exploited to achieve arbitrary 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.17.02.18CVSS 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.0/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.
-
Verify Bentley View installation existsCheck common installation paths such as C:\Program Files\Bentley\Bentley View\ or use system inventory tools to find if Bentley View software is present on the systemAffected if Bentley View is not installed on the system - not affected
-
Determine installed Bentley View versionLocate the Bentley View executable (typically BentleyView.exe) and use 'File Properties' or run 'BentleyView.exe -v' or check Windows Programs and Features for the versionAffected if Unable to determine version - further investigation needed
-
Compare version against affected rangeCompare the installed version number to 10.17.02.18 - any version lower than 10.17.02.18 is affectedAffected if Installed version is 10.17.02.18 or higher - not affected by this CVE
-
Assess SKP file handling exposureReview whether the system or its users routinely open SKP (SketchUp) files using Bentley View - check file associations, recent files, or user workflowsAffected if Bentley View with version < 10.17.02.18 is used to open SKP files, especially from untrusted sources - vulnerable to exploitation
The system is affected if Bentley View version is below 10.17.02.18 and the application is used to open SKP files, since the out-of-bounds write occurs during SKP file parsing.
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.17.02.18
Avoid opening untrusted or unknown SKP files in Bentley View. Apply vendor-provided security patches when released. Train users not to open files from untrusted sources.
Bentley View 10.17.02.18 or later
- Identify the currently installed Bentley View version via Help > About Bentley View
- Navigate to Bentley's official software download portal or contact Bentley Systems support
- Download Bentley View version 10.17.02.18 or later
- Close all Bentley View instances before proceeding with the installation
- Run the installer with administrative privileges
- Follow the installation wizard prompts to complete the upgrade
- Restart the system after installation completes
- Verify the installed version matches the target (10.17.02.18 or later) via Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43653 — 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-2022-43653 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