CVE-2022-43651
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 Use-After-Free 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. 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-18960.
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 confidenceA use-after-free vulnerability exists in Bentley View's SKP file parser. The code fails to validate the existence of an object before performing operations on it, allowing an attacker to potentially execute arbitrary code in the context of the current process by tricking a user into opening a malicious SKP file.
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 installationCheck if Bentley View is installed on the system by looking for the application in installed programs (Windows Control Panel > Programs and Features, or macOS Applications folder)Affected if Bentley View is found on the system
-
Determine installed versionRight-click the Bentley View application, select Properties, and check the Details tab for the version number, or launch Bentley View and navigate to Help > About Bentley View to view the versionAffected if Version displayed is below 10.17.02.18
-
Confirm vulnerability applicabilityThe vulnerability affects the SKP file parser - determine if the installation processes or has potential to process SKP files (a common SketchUp file format)Affected if The system runs Bentley View version 10.17.02.17 or lower and processes SKP files
A user is affected if Bentley View version 10.17.02.17 or lower is installed and the system is used to open SKP files, as the use-after-free flaw in the SKP parser can be triggered by a malicious file.
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
Users should avoid opening untrusted or unverified SKP files in Bentley View. Apply vendor-provided security updates when available.
Bentley View 10.17.02.18 or later
- Check current Bentley View version by opening the application and navigating to Help > About Bentley View
- Navigate to the official Bentley Systems software download portal or Bentley Communities support site
- Download Bentley View version 10.17.02.18 or later (the latest available version)
- Run the downloaded installer with administrator privileges
- Follow the on-screen prompts to complete the installation
- Restart Bentley View if not automatically prompted
- Verify the installed version is 10.17.02.18 or higher by checking Help > About Bentley View
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43651 — 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-43651 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