CVE-2023-50192
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-21786.
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 confidenceThis is a use-after-free vulnerability in Trimble SketchUp Viewer's SKP file parser. The vulnerability stems from the code failing to validate that an object still exists before performing operations on it, allowing an attacker to potentially execute code by leveraging freed memory through a specially crafted 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 Trimble SketchUp Viewer installationLocate SketchUp Viewer on the system - it may be a desktop application or browser plugin. Check the application version by opening the program and navigating to Help > About SketchUp Viewer, or right-click the executable and select Properties to view version informationAffected if SketchUp Viewer is installed and the version cannot be determined or is below 23.2.101 or 23.2.102
-
Compare installed version to affected rangesRecord the full version number shown in the About dialog or file Properties and compare it against the affected version thresholds: versions before 23.2.101 or before 23.2.102 (depending on which release channel the version belongs to)Affected if The installed version number is less than 23.2.101 or less than 23.2.102
-
Confirm vulnerability trigger conditionUnderstand that the use-after-free flaw exists in the SKP file parser component, which is invoked whenever SketchUp Viewer opens or processes a SKP fileAffected if The viewer is used to open SKP files from any source, with higher risk from untrusted or unknown sources
A user is affected if they have Trimble SketchUp Viewer installed with a version lower than 23.2.101 or 23.2.102 and routinely open SKP files in the viewer
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
Users should avoid opening SKP files from untrusted or unknown sources. The vendor will need to release a patch that adds proper validation checks to ensure objects exist before operations are performed on them.
SketchUp Viewer 23.2.102 or later
- 1. Visit the official Trimble SketchUp download page or check for updates within the SketchUp Viewer application
- 2. Download SketchUp Viewer version 23.2.102 or later
- 3. Close any running instances of SketchUp Viewer
- 4. Install the updated version following the on-screen prompts
- 5. Verify the installed version by checking Help > About SketchUp to confirm version 23.2.102 or higher is running
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50192 — 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-50192 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