CVE-2023-50193
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 · uneditedTrimble SketchUp Viewer SKP File Parsing Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Trimble SketchUp Viewer. 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-21787.
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 confidenceTrimble SketchUp Viewer contains a Use-After-Free vulnerability in SKP file parsing where the application fails to validate object existence before performing operations on it. This allows remote code execution in the context of the current process when a user opens 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< 23.2.101< 23.2.102CVSS 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.
-
Confirm Trimble SketchUp Viewer is installedCheck for SketchUp Viewer in installed programs (Windows: Add/Remove Programs, macOS: Applications folder, or search for 'SketchUp' in system search)Affected if The application is present on the system
-
Identify installed version numberOpen SketchUp Viewer, then go to Help > About SketchUp (Windows) or SketchUp > About SketchUp (macOS) to display the version number; alternatively, check the program's entry in Add/Remove Programs or the installer log filesAffected if Version shown is below 23.2.101 or below 23.2.102 (both ranges are affected)
-
Determine if SKP file association is activeRight-click any .skp file and verify it opens with SketchUp Viewer, or check File > Open in the application to confirm SKP files are accessibleAffected if SKP files can be opened by the viewer (this is the default behavior and required for exploitation)
You are affected if Trimble SketchUp Viewer is installed and the version is either below 23.2.101 or below 23.2.102, as both version ranges contain the Use-After-Free vulnerability in 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 · scoped23.2.10123.2.102
Apply vendor-supplied patches or update to the latest version of Trimble SketchUp Viewer; avoid opening untrusted SKP files from unknown sources.
Upgrade to SketchUp Viewer version 23.2.102 or later
- 1. Verify the current installed version of Trimble SketchUp Viewer by opening the application and navigating to Help > About SketchUp
- 2. If the installed version is earlier than 23.2.102, download the latest version from the official Trimble website or authorized distribution channel
- 3. Close all instances of SketchUp Viewer before proceeding with the update
- 4. Run the installer for version 23.2.102 or later
- 5. Follow the on-screen installation prompts to complete the update
- 6. After installation, verify the new version by checking Help > About SketchUp to confirm version 23.2.102 or higher is installed
- 7. Test that SKP files can be opened and parsed correctly in the updated version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50193 — 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-2023-50193 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