CVE-2011-2478
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 · uneditedGoogle SketchUp before 8 does not properly handle edge geometry in SketchUp (aka .SKP) files, which allows remote attackers to execute arbitrary code via a crafted 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 confidenceGoogle SketchUp before version 8 contains a vulnerability in its file parsing logic for edge geometry within SketchUp (.SKP) files. When processing a specially crafted malicious .SKP file, the application fails to properly validate or sanitize the edge geometry data, allowing an attacker to trigger memory corruption and achieve arbitrary code execution with the privileges of the user running SketchUp.
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<= 7.1= 6.0= 7.0= 7.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed SketchUp versionOpen SketchUp and go to Help > About SketchUp, or check Programs and Features in Control Panel for the installed versionAffected if The version listed is 6.0, 7.0, 7.1, or any version 7.1 or lower
-
Verify .SKP file associationCheck if .SKP files are associated with SketchUp by right-clicking any .SKP file and viewing the 'Opens with' property, or check Default Programs > Set AssociationsAffected if SketchUp is set as the default handler for .SKP files and the version is affected
-
Identify recent .SKP file activityCheck the SketchUp recent files list (File > Recent Files) or search the user profile for .SKP files that may have been openedAffected if The application has been used to open .SKP files, indicating the vulnerable parsing code path could be triggered
A user is affected if they have Google SketchUp version 7.1 or earlier installed and use the application to open .SKP files, as the vulnerability lies in the edge geometry parsing of those files.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Google SketchUp to version 8 or later. Until upgraded, exercise extreme caution when opening .SKP files from untrusted sources, and consider disabling file associations or sandboxing the application.
Google SketchUp 8 or later
- 1. Back up any existing SketchUp projects and settings
- 2. Uninstall the current version of Google SketchUp (versions 6.0, 7.0, or 7.1)
- 3. Download Google SketchUp 8 or a later stable version from the official Google SketchUp website
- 4. Install the new version by running the downloaded installer
- 5. Verify the installation by launching SketchUp and confirming the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2478 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-2478 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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