Sketchup ViewerApplication · Trimble

CVE-2024-9725

HIGH · 7.8 CVSS v3.1 Published 2024-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 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-24109.

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 confidence

A Use-After-Free vulnerability exists in Trimble SketchUp Viewer's SKP file parser. The parser fails to validate that an object still exists before performing operations on it, allowing an attacker to free an object and then trigger operations on the dangling pointer, leading to arbitrary code execution in the context of the current process.

MitigationDo not open untrusted SKP files in SketchUp Viewer. Keep the software updated when patches become available. Consider running SketchUp Viewer in sandboxed or isolated environments to limit impact of potential exploitation.

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:= 22.0.316.0

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.1/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 SketchUp Viewer is installed
    On Windows, check for the executable at C:\Program Files\Trimble\SketchUp Viewer\SketchUpViewer.exe or search for SketchUpViewer.exe using Get-ChildItem -Path "C:\Program Files" -Recurse -Filter "SketchUpViewer.exe" -ErrorAction SilentlyContinue
    Affected if SketchUp Viewer executable exists on the system
  2. Determine installed version
    Right-click SketchUpViewer.exe, select Properties, then view the File Version tab. Alternatively, run: (Get-Item "C:\Program Files\Trimble\SketchUp Viewer\SketchUpViewer.exe").VersionInfo.FileVersion
    Affected if Version displayed is exactly 22.0.316.0
  3. Confirm application handles SKP files
    Verify the software is configured to open .skp file extensions or check recent file associations using assoc .skp in Command Prompt
    Affected if SketchUp Viewer is associated with .skp file extension or has been used to open SKP files
  4. Identify exposure to untrusted SKP files
    Review recent activity: check Documents or Downloads folders for .skp files of unknown origin, or review browser download history for .skp file downloads
    Affected if User has downloaded or received SKP files from untrusted or unknown sources

User is affected if SketchUp Viewer version 22.0.316.0 is installed AND the system processes or has processed untrusted 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Do not open untrusted SKP files in SketchUp Viewer. Keep the software updated when patches become available. Consider running SketchUp Viewer in sandboxed or isolated environments to limit impact of potential exploitation.

Fix this in Sketchup Viewer Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-9725 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-9725 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