dbcve.org
ChromeWeb browser · Google

CVE-2011-0781

HIGH · 7.5 CVSS v2.0 Published 2011-02-04
Fix available
A fix is available. Upgrade to 9.0.597.84 or later.
See remediation →
84/100
Remediation priority · High
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 9.0.597.84 does not properly handle autofill profile merging, which has unspecified impact and remote attack vectors.

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 · moderate confidence

Google Chrome before version 9.0.597.84 contains a vulnerability in the autofill feature where profile merging is not properly handled, allowing remote attackers to exploit the browser through unspecified vectors with HIGH severity impact.

MitigationUpgrade Google Chrome to version 9.0.597.84 or later to address the autofill profile merging vulnerability; ensure patch management processes include browser version validation.

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:< 9.0.597.84

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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
    Open Chrome and navigate to chrome://version, or click the wrench icon > About Google Chrome. The version number is displayed at the top of the About dialog.
    Affected if The displayed version is lower than 9.0.597.84 (for example, 9.0.597.83, 9.0.597.70, 8.x, etc.)
  2. Confirm autofill feature is enabled
    Navigate to chrome://settings/autofill or go to Settings > Autofill settings. Check if any autofill profiles or saved addresses exist.
    Affected if Autofill profiles or addresses are saved and enabled in the browser settings.
  3. Check Chrome release channel
    In the About Google Chrome dialog, note whether the installation is Stable, Beta, Dev, or Canary. Older versions were commonly distributed on beta/dev channels before the fix.
    Affected if Running a pre-9.0.597.84 release on any channel indicates potential exposure.

You are affected if your installed Google Chrome version is below 9.0.597.84 AND you have autofill profiles or saved addresses enabled in the browser.

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.

From vendor data
Upgrade available Upgrade to 9.0.597.84 or later
Fixed in 9.0.597.84
Interim mitigation

Upgrade Google Chrome to version 9.0.597.84 or later to address the autofill profile merging vulnerability; ensure patch management processes include browser version validation.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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