dbcve.org
Sketchup ViewerApplication · Trimble

CVE-2023-50194

HIGH · 7.8 CVSS v3.0 Published 2024-05-03
Fix available
A fix is available. Upgrade to 23.2.101 / 23.2.102 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Trimble SketchUp Viewer SKP File Parsing Out-Of-Bounds Read 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 read past the end of an allocated object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-21788.

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 · moderate confidence

An out-of-bounds read vulnerability exists in Trimble SketchUp Viewer's SKP file parser due to insufficient validation of user-supplied data during file parsing. The lack of proper bounds checking allows reading past the end of an allocated object, which can be leveraged to achieve remote code execution in the context of the current process.

MitigationAvoid opening untrusted or unknown SKP files until a vendor patch is available. Restrict file handling to trusted sources and apply network segmentation as a defense-in-depth measure.

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
Sketchup ViewerApplication
Affected:< 23.2.101< 23.2.102

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Trimble SketchUp Viewer is installed
    Look for the application in Program Files (Windows) or /Applications (macOS), or check installed programs list via system settings or registry
    Affected if Trimble SketchUp Viewer is present on the system
  2. Determine the installed version of SketchUp Viewer
    Right-click the executable and select Properties > Details, or use the application's Help > About menu, or check the version in Add/Remove Programs
    Affected if Version cannot be determined or is earlier than 23.2.101 or 23.2.102
  3. Compare installed version to affected ranges
    Note the full version number (e.g., 23.2.100, 23.1.326) and compare against the affected versions: any version less than 23.2.101 or less than 23.2.102 is vulnerable
    Affected if Installed version is less than 23.2.101 or less than 23.2.102
  4. Identify if SKP file handling is used
    The vulnerability triggers when parsing specially crafted SKP files - check if the viewer is used to open files from untrusted sources or if file association with .skp exists
    Affected if The application is used to open .skp files, particularly from untrusted sources

The environment is affected if Trimble SketchUp Viewer is installed and the version is below 23.2.101 or 23.2.102, and the application is used to open .skp files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 23.2.101 / 23.2.102 or later
Fixed in 23.2.10123.2.102
Interim mitigation

Avoid opening untrusted or unknown SKP files until a vendor patch is available. Restrict file handling to trusted sources and apply network segmentation as a defense-in-depth measure.

Recommended fix Moderate confidence

Upgrade to SketchUp Viewer version 23.2.101 or later

  1. Check the current installed version of Trimble SketchUp Viewer (typically found in Help > About SketchUp Viewer or the application properties)
  2. Navigate to the official Trimble website or authorized download center to obtain the fixed version
  3. Download SketchUp Viewer version 23.2.101 or a later stable release
  4. Uninstall the current vulnerable version of SketchUp Viewer from the system
  5. Install the downloaded fixed version (23.2.101 or later)
  6. Restart the application and verify the version number matches the fixed release
Caveat Minor: Ensure compatibility of existing SKP files with the new version; no major breaking changes expected for viewing functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sketchup Viewer Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-50194 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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