ChromeWeb browser · Google
CVE-2010-2302
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 · uneditedUse-after-free vulnerability in WebCore in WebKit in Google Chrome before 5.0.375.70 allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via vectors involving remote fonts in conjunction with shadow DOM trees, aka rdar problem 8007953. NOTE: this might overlap CVE-2010-1771.
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 confidenceUse-after-free vulnerability in WebCore (WebKit's rendering engine) in Google Chrome before version 5.0.375.70. The flaw occurs when processing remote fonts in conjunction with shadow DOM trees, leading to memory corruption that can be exploited for denial of service or potentially arbitrary code execution by remote attackers.
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
ChromeWeb browser
< 5.0.375.70= 11.2= 11.3= 10= 11= 10= 11CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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 Google Chrome version on Windows/Mac/LinuxNavigate to chrome://version in the Chrome browser or run 'google-chrome --version' in command lineAffected if Version is less than 5.0.375.70
-
Check installed Chrome package on Suse/OpenSuseRun 'rpm -qa | grep -i chrome' or 'dpkg -l | grep -i chrome' to list installed Chrome packages, then check version with 'rpm -qi <package-name>'Affected if Chrome version is less than 5.0.375.70 or Chrome package is present from the affected Suse/OpenSuse releases (11.2, 11.3, SLE 10, SLE 11)
-
Check WebKit package version on Suse/OpenSuseRun 'rpm -qa | grep -i webkit' to list WebKit packages, then check version with 'rpm -qi <package-name>'Affected if WebKit version corresponds to the vulnerable Chrome version (< 5.0.375.70) shipped with affected Suse distributions
User is affected if Google Chrome or the Chrome/WebKit package shipped with the system is version 5.0.375.69 or lower, specifically on Suse/OpenSuse 11.2, 11.3, SLE 10, or SLE 11.
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 · scoped5.0.375.70
Upgrade Google Chrome to version 5.0.375.70 or later. In enterprise environments, test for compatibility issues after the upgrade before broad deployment.
Chrome 5.0.375.70 or later (recommend current stable release)
- 1. Verify current Chrome version by navigating to chrome://settings/help
- 2. If running a version before 5.0.375.70, download and install the latest stable Chrome version from official Google source (google.com/chrome)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-2302 — 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-2010-2302 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