dbcve.org
SketchupApplication · Trimble

CVE-2024-9730

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

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

Memory corruption vulnerability in Trimble SketchUp Viewer's SKP file parser due to insufficient validation of user-supplied data during file parsing. The lack of bounds checking or proper input validation allows attackers to corrupt memory and achieve arbitrary code execution in the context of the current process.

MitigationAvoid opening untrusted SKP files from unknown sources. Apply vendor patches when available. Consider network isolation or sandboxing for SketchUp Viewer 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
SketchupApplication
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. Locate SketchUp Viewer executable
    Find the main SketchUp Viewer executable (typically SketchUp.exe) in the installation directory, commonly in Program Files/Trimble/SketchUp/SketchUp Viewer or Program Files/SketchUp/SketchUp Viewer
    Affected if The executable exists and is the SketchUp Viewer application
  2. Check installed version number
    Right-click the SketchUp.exe file, select Properties, then go to the Details tab and check the Product version field. Alternatively, open SketchUp Viewer and navigate to Help > About SketchUp to view the version
    Affected if The version displayed is exactly 22.0.316.0
  3. Confirm SKP file handler is present
    Verify that .skp file association is configured in Windows by checking default programs settings or looking for file type associations in the Windows Registry under HKCR\.skp
    Affected if The .skp file extension is associated with SketchUp Viewer, meaning the vulnerable parser can be triggered by opening files
  4. Identify if untrusted SKP files could be processed
    Check if SketchUp Viewer has been used to open files from untrusted or unknown sources, or if the application is configured to auto-open attached SKP files from email or web downloads
    Affected if Users open or could open SKP files from untrusted sources, which would trigger the vulnerable parser

A user is affected if SketchUp Viewer version 22.0.316.0 is installed and the application is used to open SKP files, since the vulnerability lies in the SKP file parser's lack of bounds checking during file parsing.

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

Avoid opening untrusted SKP files from unknown sources. Apply vendor patches when available. Consider network isolation or sandboxing for SketchUp Viewer to limit impact of potential exploitation.

Fix this in Sketchup Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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