dbcve.org
ChromeWeb browser · Google

CVE-2010-2299

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
The Clipboard::DispatchObject function in app/clipboard/clipboard.cc in Google Chrome before 5.0.375.70 does not properly handle CBF_SMBITMAP objects in a ViewHostMsg_ClipboardWriteObjectsAsync message, which might allow remote attackers to execute arbitrary code via vectors involving crafted data from the renderer process, related to a "Type Confusion" issue.

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

A type confusion vulnerability exists in Google Chrome's Clipboard::DispatchObject function where CBF_SMBITMAP objects are not properly validated within ViewHostMsg_ClipboardWriteObjectsAsync messages, allowing a malicious renderer process to trigger arbitrary code execution through crafted clipboard data.

MitigationUpgrade Google Chrome to version 5.0.375.70 or later to address this type confusion vulnerability in the clipboard handling code.

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 Chrome version
    Navigate to chrome://version in the Chrome browser or run 'google-chrome --version' from command line
    Affected if The version displayed is less than 5.0.375.70 (e.g., 5.0.x.y where x < 375, or any version 4.x or earlier)
  2. Verify clipboard feature is enabled
    Check that clipboard operations are permitted - this is enabled by default in Chrome. No specific setting to disable clipboard exists for normal usage.
    Affected if Clipboard functionality is active (default state) and the browser handles clipboard write operations from web content
  3. Identify if renderer processes can write to clipboard
    In Chrome's sandbox architecture, verify that the renderer process has clipboard write privileges through ViewHostMsg_ClipboardWriteObjectsAsync IPC messages
    Affected if The browser processes clipboard write requests from web pages or extensions (standard behavior in vulnerable versions)

A user is affected if they are running any version of Google Chrome prior to 5.0.375.70 with clipboard functionality enabled (the default state), as the type confusion in Clipboard::DispatchObject can be triggered by crafted clipboard data from a malicious renderer process.

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

Upgrade Google Chrome to version 5.0.375.70 or later to address this type confusion vulnerability in the clipboard handling code.

Recommended fix High confidence

Chrome 5.0.375.70 or later (recommended: latest stable release)

  1. Open Chrome and navigate to chrome://settings/help to check the current version
  2. If the version is older than 5.0.375.70, download the latest stable Chrome version from the official Google Chrome website (google.com/chrome)
  3. Install the downloaded Chrome version, allowing it to replace the existing installation
  4. Restart Chrome to complete the update
  5. Verify the update was successful by checking chrome://settings/help again
Caveat Chrome 5.0 was a major version release from Chrome 4.x; legacy extensions or plugins may require updates. However, the primary concern is security remediation.

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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