dbcve.org
ChromeWeb browser · Google

CVE-2011-3086

HIGH · 10.0 CVSS v2.0 Published 2012-05-16
Fix available
A fix is available. Upgrade to after 19.0.1084.45 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 Google Chrome before 19.0.1084.46 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving a STYLE element.

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 Google Chrome browser versions before 19.0.1084.46 allows remote attackers to cause denial of service or potentially achieve arbitrary code execution through malicious manipulation of a STYLE element in the Document Object Model (DOM).

MitigationUpdate Google Chrome to version 19.0.1084.46 or later. For enterprise environments, deploy the update via centralized software distribution mechanisms and verify successful installation across all affected clients.

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:<= 19.0.1084.45

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
    Check for Chrome executable: On Windows, look for chrome.exe in Program Files or AppData; on macOS, check /Applications for Chrome.app; on Linux, run which google-chrome or check /usr/bin/google-chrome
    Affected if Chrome browser is present on the system
  2. Retrieve installed Chrome version number
    On Windows, open Chrome and navigate to chrome://settings/help or run chrome --version from command line; on macOS, right-click Chrome.app > Get Info or run /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version; on Linux, run google-chrome --version
    Affected if Unable to determine version (Chrome may be installed but not accessible)
  3. Compare version against affected range
    Parse the version number obtained and compare numerically against 19.0.1084.45. The format is major.minor.patch.build (e.g., 19.0.1084.45). Note that versions before 19.0.1084.46 (such as 19.0.1084.45, 18.x, 17.x, etc.) are all affected.
    Affected if Installed version is 19.0.1084.45 or any earlier version (19.0.1084.x where x is 45 or lower, or any 18.x/17.x/16.x release)

User is affected if Google Chrome is installed and the running version is 19.0.1084.45 or any earlier version (anything before 19.0.1084.46).

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 a release after 19.0.1084.45
Interim mitigation

Update Google Chrome to version 19.0.1084.46 or later. For enterprise environments, deploy the update via centralized software distribution mechanisms and verify successful installation across all affected clients.

Recommended fix High confidence

Chrome 19.0.1084.46 (or later stable release)

  1. Open Chrome and navigate to Chrome > About Google Chrome to view the current version.
  2. If the version is 19.0.1084.45 or earlier, click 'Update' to install the fixed release (19.0.1084.46 or later).
  3. If automatic updates are disabled, download the latest Chrome installer from https://www.google.com/chrome/ and run it to update.
  4. Restart the browser after the update completes.
  5. Verify the installed version is 19.0.1084.46 or later.
Caveat Minor risk of extension or plugin incompatibility after upgrade.

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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