dbcve.org
Sketchup ViewerApplication · Trimble

CVE-2023-50187

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 Memory Corruption 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 memory corruption condition. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-20789.

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

A memory corruption vulnerability exists in Trimble SketchUp Viewer's SKP file parser due to improper validation of user-supplied data during file parsing. An attacker can exploit this by tricking a user into opening a malicious SKP file, leading to arbitrary code execution in the context of the current process.

MitigationAvoid opening SKP files from untrusted sources and apply vendor patches when available. Implement network-based file scanning and user awareness training to reduce exposure.

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. Verify Trimble SketchUp Viewer is installed
    On Windows, check Program Files for 'Trimble SketchUp Viewer' folder or look in Add/Remove Programs. On macOS, check /Applications for SketchUp Viewer.app
    Affected if The application is present on the system
  2. Check installed version number
    On Windows, right-click SketchUpViewer.exe > Properties > Details tab to view FileVersion. On macOS, right-click SketchUp Viewer.app > Show Package Contents > Contents/Info.plist, look for CFBundleShortVersionString
    Affected if Version is less than 23.2.101 or between 23.2.101 and 23.2.102 (exclusive of 23.2.102)
  3. Confirm the SKP file handling component is present
    Locate the main executable (SketchUpViewer.exe on Windows, SketchUp Viewer on macOS) and verify it exists - this contains the vulnerable SKP parser module
    Affected if The viewer executable exists and can process SKP files

If Trimble SketchUp Viewer is installed with a version lower than 23.2.102, opening a malicious SKP file could trigger arbitrary code execution in the current user context.

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 SKP files from untrusted sources and apply vendor patches when available. Implement network-based file scanning and user awareness training to reduce exposure.

Recommended fix Moderate confidence

Upgrade to SketchUp Viewer version 23.2.101 or later

  1. 1. Open Trimble SketchUp Viewer
  2. 2. Navigate to the Help or About section
  3. 3. Check the current version number
  4. 4. If version is below 23.2.101 or 23.2.102, download the latest version from the official Trimble website
  5. 5. Uninstall the current version
  6. 6. Install the updated version (23.2.101 or later)
  7. 7. Restart the application and verify the version

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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-50187 — 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-50187 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