dbcve.org
ChromeWeb browser · Google

CVE-2011-3091

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 the IndexedDB implementation in Google Chrome before 19.0.1084.46 allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown 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

Use-after-free memory corruption vulnerability in Google Chrome's IndexedDB implementation (browser database API) before version 19.0.1084.46. Allows remote attackers to potentially execute arbitrary code or cause denial of service by freeing memory that is still being referenced.

MitigationUpdate Google Chrome to version 19.0.1084.46 or later. In enterprise environments, deploy the update via centralized software distribution/management tools.

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. Confirm Google Chrome is installed
    Check for chrome.exe on Windows (C:\Program Files\Google\Chrome\Application\), chrome on macOS (/Applications/Google Chrome.app), or google-chrome on Linux (typically in /usr/bin/)
    Affected if Google Chrome browser is present on the system
  2. Determine installed Chrome version
    Open chrome://version in the Chrome address bar, or run 'google-chrome --version' from command line, or check the executable properties
    Affected if Version displayed is 19.0.1084.45 or lower
  3. Compare against affected version range
    Compare your installed version number to the affected range: any version <= 19.0.1084.45
    Affected if Installed version is 19.0.1084.45 or any earlier version (e.g., 19.0.1084.40, 18.x, 17.x, etc.)
  4. Verify IndexedDB is accessible
    IndexedDB is enabled by default in Chrome. To confirm, open chrome://settings and search for 'IndexedDB' in content settings, or visit a site that uses IndexedDB (such as any HTML5 database demo)
    Affected if IndexedDB is enabled (default state) - the vulnerability applies regardless of whether the feature has been explicitly used

You are affected if Google Chrome is installed AND the version is 19.0.1084.45 or lower, since the use-after-free flaw in IndexedDB exists in those versions regardless of whether IndexedDB has been actively used.

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. In enterprise environments, deploy the update via centralized software distribution/management tools.

Recommended fix High confidence

Chrome 19.0.1084.46 or later (any stable release beyond 19.0.1084.45)

  1. Open Google Chrome
  2. Click the Chrome menu (three dots icon) in the top-right corner
  3. Select 'Help' from the dropdown menu
  4. Click 'About Google Chrome'
  5. The browser will check for updates automatically
  6. If version 19.0.1084.46 or later is available, click 'Update Google Chrome'
  7. Restart the browser to complete the update
  8. After restart, verify the version by returning to 'About Google Chrome' and confirming the version is 19.0.1084.46 or higher
Caveat Chrome updates typically include backward-compatible changes, but older web applications relying on specific IndexedDB behavior may need testing

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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