SketchupApplication · Google

CVE-2012-4894

HIGH · 9.3 CVSS v2.0 Published 2012-10-05
Fix available
A fix is available. Upgrade to after 8.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Google SketchUp before 8.0.14346 (aka 8 Maintenance 3) allows user-assisted remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted SKP file.

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 Google SketchUp versions before 8.0.14346 allows remote code execution or denial of service via a specially crafted SKP file. The attack is user-assisted, requiring the victim to open a malicious file.

MitigationUpgrade to Google SketchUp 8.0.14346 (8 Maintenance 3) or later. Avoid opening SKP files from untrusted sources.

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:<= 8.0= 6.0= 7.0= 7.1= 8.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
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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. Confirm Google SketchUp is installed
    Windows: Check Program Files/Google SketchUp folder, or look for 'SketchUp' in Add/Remove Programs. Mac: Check /Applications folder for SketchUp.app
    Affected if Google SketchUp software is present on the system
  2. Locate the SketchUp executable and retrieve version
    Windows: Right-click SketchUp.exe, select Properties, view Version tab. Mac: Right-click SketchUp.app, select Get Info, view Version field
    Affected if Version information cannot be retrieved (software may be partially installed or corrupted)
  3. Compare installed version to affected range
    Check if version is 6.0, 7.0, 7.1, or 8.0 (or any version <= 8.0)
    Affected if Installed version is 6.0, 7.0, 7.1, or 8.0, or any 8.0.x version before 8.0.14346
  4. Verify if the application can open SKP files
    Check file association for .SKP files or confirm the application can still be launched and open model files
    Affected if SketchUp is installed and can be used to open SKP files, making the vulnerability accessible
  5. Confirm the patch version if installed
    If version shows 8.0.x, verify the full build number: look for 8.0.14346 or higher in the About SketchUp dialog (Help > About SketchUp)
    Affected if Version is 8.0.x but build number is below 14346, or build number cannot be confirmed

User is affected if Google SketchUp version 6.0, 7.0, 7.1, or 8.0 (including 8.0.x versions before 8.0.14346) is installed and can be 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 a release after 8.0
Interim mitigation

Upgrade to Google SketchUp 8.0.14346 (8 Maintenance 3) or later. Avoid opening SKP files from untrusted sources.

Recommended fix High confidence

Google SketchUp 8.0.14346 (8 Maintenance 3) or later

  1. Identify the current Google SketchUp version installed on the system
  2. Navigate to the official Google SketchUp download page or trusted software distribution channel
  3. Download Google SketchUp version 8.0.14346 (8 Maintenance 3) or a later stable release
  4. Close any running SketchUp instances
  5. Install the downloaded update following the on-screen prompts
  6. Launch SketchUp and verify the version number reflects the update (Help > About SketchUp)
Caveat Upgrading from SketchUp 6.0 or 7.x to version 8 may introduce compatibility changes with older project files and plugins; test critical files before production use

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

Fix this in Sketchup Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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