dbcve.org
Sketchup ViewerApplication · Trimble

CVE-2024-9719

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-24103.

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

This is a Use-After-Free vulnerability in Trimble SketchUp Viewer's SKP file parser. The flaw occurs because the code fails to validate that an object exists before performing operations on it, leading to a dangling pointer that can be exploited for remote code execution when a user opens a malicious SKP file.

MitigationApply the vendor patch from Trimble when available. Until then, enforce user awareness to avoid opening SKP files from untrusted sources and consider disabling file associations or using application sandboxing 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:= 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
    Check for Trimble SketchUp Viewer in the list of installed applications (Windows: Add/Remove Programs or Settings > Apps; macOS: Applications folder or System Preferences > Applications). Look for executables named SketchUp, SketchUpViewer, or similar.
    Affected if Trimble SketchUp Viewer is installed on the system
  2. Identify the installed version
    Locate the installed SketchUp Viewer application. Right-click the executable (commonly in Program Files or Program Files (x86) on Windows, or /Applications on macOS), select Properties, and check the Version tab. Alternatively, right-click the .exe and select 'View info' or check the file details.
    Affected if The version displayed is exactly 22.0.316.0
  3. Confirm the SKP file parser component is present
    Verify the application contains the SKP file parsing libraries. Check the installation directory for files with .dll or .framework extensions related to SKP parsing (such as SKPReader, Model, or similar naming).
    Affected if The SKP parsing component exists in the installation directory
  4. Check for active file associations or recent usage
    Open the application and check File > Open or examine recent files. On Windows, also check HKEY_CURRENT_USER\Software\Classes\.skp or HKEY_LOCAL_MACHINE\Software\Classes\.skp in the Registry to see if .skp files are associated with SketchUp Viewer.
    Affected if SKP files are associated with the installed viewer or recent SKP files appear in the application

If Trimble SketchUp Viewer version 22.0.316.0 is installed and SKP file handling is enabled or has been used, the environment is affected by this vulnerability.

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

Apply the vendor patch from Trimble when available. Until then, enforce user awareness to avoid opening SKP files from untrusted sources and consider disabling file associations or using application sandboxing to reduce exposure.

Fix this in Sketchup Viewer Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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