dbcve.org
Chrome OsOperating system · Google

CVE-2011-0485

HIGH · 10.0 CVSS v2.0 Published 2011-01-14
Fix available
A fix is available. Upgrade to 8.0.552.237 / 8.0.552.344 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 Chrome before 8.0.552.237 and Chrome OS before 8.0.552.344 do not properly handle speech data, which allows remote attackers to execute arbitrary code via unspecified vectors that lead to a "stale pointer."

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

This is a stale pointer vulnerability in the speech data handling component of Google Chrome and Chrome OS. The vulnerability allows remote attackers to execute arbitrary code through unspecified vectors that cause a stale (use-after-free) pointer condition in the speech processing code.

MitigationUpdate Google Chrome to version 8.0.552.237 or later, and Chrome OS to version 8.0.552.344 or later. Organizations should deploy the updated browser versions via their patch management 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
Chrome OsOperating system
Affected:< 8.0.552.344
ChromeWeb browser
Affected:< 8.0.552.237

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. Verify Google Chrome is installed
    Run 'google-chrome --version' on Linux/Mac, or check C:\Program Files\Google\Chrome\Application\chrome.exe on Windows. On Chrome OS, this is inherent to the OS installation.
    Affected if Google Chrome or Chrome OS is not installed on the system
  2. Determine the installed Chrome version
    Run 'google-chrome --version' or 'chrome://version' in the browser address bar. On Chrome OS, access chrome://version or check System Settings > About Chrome OS.
    Affected if The version cannot be determined or is not displayed
  3. Compare against vulnerable Chrome versions
    Compare your installed Chrome version to 8.0.552.237. Versions below this threshold (8.x series less than 8.0.552.237) are affected.
    Affected if Installed Chrome version is less than 8.0.552.237
  4. Compare against vulnerable Chrome OS versions
    On Chrome OS, check the version shown in System Settings > About Chrome OS or chrome://version. Compare to 8.0.552.344.
    Affected if Installed Chrome OS version is less than 8.0.552.344

A system is affected if Google Chrome version is less than 8.0.552.237 or Chrome OS version is less than 8.0.552.344, as the stale pointer vulnerability exists only in these vulnerable versions of the speech data handling component.

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 8.0.552.237 / 8.0.552.344 or later
Fixed in 8.0.552.2378.0.552.344
Interim mitigation

Update Google Chrome to version 8.0.552.237 or later, and Chrome OS to version 8.0.552.344 or later. Organizations should deploy the updated browser versions via their patch management systems.

Recommended fix High confidence

Chrome 8.0.552.237 or later / Chrome OS 8.0.552.344 or later

  1. Check the current Chrome version by navigating to chrome://settings/help or chrome://version in the address bar
  2. Check the current Chrome OS version by clicking on the status area and selecting 'Settings' > 'About Chrome OS'
  3. If the version is below 8.0.552.237 (Chrome) or below 8.0.552.344 (Chrome OS), initiate an update through the browser's built-in update mechanism
  4. For Chrome: Click 'Update Google Chrome' when prompted, or manually download the latest stable version from the official Google Chrome website
  5. For Chrome OS: Ensure the device is connected to the internet and check for system updates via Settings > About Chrome OS > Check for updates
  6. Restart the browser or device after the update is complete
  7. Verify the update was successful by checking that the version is now 8.0.552.237 or higher for Chrome, or 8.0.552.344 or higher for Chrome OS
Caveat Chrome 8 was a major version upgrade; users should review new features and default settings, but no critical functionality breaking changes are expected from this security update

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

Fix this in Chrome Os 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-2011-0485 — 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-2011-0485 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