ChromeWeb browser · Google
CVE-2011-3085
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 · uneditedThe Autofill feature in Google Chrome before 19.0.1084.46 does not properly restrict field values, which allows remote attackers to cause a denial of service (UI corruption) and possibly conduct spoofing attacks via vectors involving long values.
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 confidenceThe Autofill feature in Google Chrome versions prior to 19.0.1084.46 fails to properly restrict the length of field values, allowing attackers to inject excessively long strings that corrupt the user interface and potentially enable spoofing attacks by manipulating visible form data.
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
<= 19.0.1084.45CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine if Google Chrome is installedOpen Chrome and navigate to chrome://version or check for chrome.exe on Windows (typically in Program Files/Google/Chrome/Application/) or /Applications/Google Chrome on macOSAffected if Google Chrome browser is present on the system
-
Check the installed Chrome version numberIn Chrome address bar, type chrome://version and look for the version number displayed (e.g., 19.0.1084.45, 19.0.1084.46, etc.)Affected if The displayed version is 19.0.1084.45 or lower (any version up to and including 19.0.1084.45)
-
Verify if Autofill is enabledIn Chrome, go to Settings > Autofill and Forms > Autofill settings, or navigate to chrome://settings/autofillAffected if Autofill is turned ON (the vulnerability requires Autofill feature to be active for exploitation)
-
Confirm affected version rangeCompare your installed version against the affected range: any version <= 19.0.1084.45 is vulnerable; versions >= 19.0.1084.46 contain the fixAffected if Version is 19.0.1084.45 or earlier AND Autofill is enabled
You are affected if you have Google Chrome version 19.0.1084.45 or earlier installed with Autofill feature enabled, as the vulnerability exists in the Autofill component's lack of field value length restrictions.
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.
From vendor dataUpgrade Chrome to version 19.0.1084.46 or later, which contains proper field value length restrictions in the Autofill component.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3085 — 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-2011-3085 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