dbcve.org
ChromeWeb browser · Google

CVE-2010-2300

HIGH · 10.0 CVSS v2.0 Published 2010-06-15
Fix available
A fix is available. Upgrade to 5.0.375.70 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
Use-after-free vulnerability in the Element::normalizeAttributes function in dom/Element.cpp in WebCore in WebKit in Google Chrome before 5.0.375.70 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via vectors related to handlers for DOM mutation events, aka rdar problem 7948784. NOTE: this might overlap CVE-2010-1759.

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

Use-after-free vulnerability in WebKit's Element::normalizeAttributes function allows remote attackers to execute arbitrary code via specially crafted DOM mutation event handlers, causing memory corruption. The flaw exists in Google Chrome versions prior to 5.0.375.70.

MitigationUpdate Google Chrome to version 5.0.375.70 or later to patch this vulnerability. Organizations should ensure browser update mechanisms are enabled and deploy patched versions to all affected systems.

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
Affected:< 5.0.375.70

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Google Chrome version
    Open Google Chrome, click the wrench icon (Tools menu), then click 'About Google Chrome', or navigate to chrome://version in the address bar. Note the version number displayed.
    Affected if The displayed version is less than 5.0.375.70 (for example, 5.0.375.60, 5.0.375.55, or any 4.x.x or 3.x.x version).
  2. Verify Chrome update status
    Click the wrench icon, select 'About Google Chrome', and check whether updates are available or if the browser reports it is up to date.
    Affected if The browser reports an available update or indicates it cannot check for updates, suggesting the installed version may be outdated.
  3. Check Chrome's build date (optional confirmation)
    Navigate to chrome://version and locate the 'Profile path' or 'Command Line' entries. The build timestamp can sometimes be cross-referenced with release dates around May-June 2010.
    Affected if The build was created before the patched version release date of June 2010.

A user is affected if their installed Google Chrome version is any version number lower than 5.0.375.70, regardless of operating system or configuration.

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 5.0.375.70 or later
Fixed in 5.0.375.70
Interim mitigation

Update Google Chrome to version 5.0.375.70 or later to patch this vulnerability. Organizations should ensure browser update mechanisms are enabled and deploy patched versions to all affected systems.

Recommended fix High confidence

Chrome 5.0.375.70 or later

  1. Ensure Google Chrome is installed on the system
  2. Open Google Chrome and navigate to the Help menu (three-dot menu > Help) or go to chrome://settings/help
  3. Chrome will automatically check for and apply updates. If an update is available, let it download and install
  4. Alternatively, download the latest stable version of Google Chrome from the official website (google.com/chrome)
  5. Restart Chrome after the update completes
  6. Verify the version by navigating to chrome://settings/help - it should show version 5.0.375.70 or later

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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