CVE-2023-50190
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 Out-Of-Bounds Write 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 proper validation of user-supplied data, which can result in 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-21784.
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 Trimble SketchUp Viewer's SKP file parsing due to insufficient validation of user-supplied data. The lack of proper bounds checking allows writing past the end of an allocated buffer, enabling remote code execution in the context of the current process. Exploitation requires user interaction via 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.
-
Identify installed SketchUp Viewer versionOpen SketchUp Viewer and navigate to Help > About SketchUp, or check the application version in the Windows Programs and Features / macOS Applications listAffected if The version shown is below 23.2.101 or 23.2.102 (depending on your release branch)
-
Confirm the application processes SKP filesVerify that the SketchUp Viewer installation includes SKP file association or that you can open .skp files through the viewerAffected if SKP file handling is enabled and the viewer can open model files
-
Check for recent SKP file opening activityReview recently opened files in the application (File > Recent Files) or examine browser/download history if using the web viewer versionAffected if Untrusted or unverified SKP files have been opened recently
-
Verify patch availability from vendorCheck Trimble's official support or update mechanism within SketchUp Viewer for available security updatesAffected if No security update has been applied and the running version remains in the affected range
You are affected if SketchUp Viewer is installed with a version lower than 23.2.101 or 23.2.102 and the application processes or has processed SKP files.
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
Avoid opening untrusted or unverified SKP files until an official patch is available. Apply vendor-supplied security updates promptly.
SketchUp Viewer version 23.2.102 or later
- 1. Close any running instances of Trimble SketchUp Viewer
- 2. Backup any important SKP files or user data
- 3. Download the latest version of Trimble SketchUp Viewer from the official Trimble website or authorized distribution channel
- 4. Run the installer and follow the prompts to complete the installation
- 5. Verify the installed version is 23.2.102 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50190 — 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-50190 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