dbcve.org
ChromeWeb browser · Google

CVE-2011-3909

MEDIUM · 5.0 CVSS v2.0 Published 2011-12-13
Fix available
A fix is available. Upgrade to 5.1 / 5.1.4 or later.
See remediation →
59/100
Remediation priority · Elevated
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
The Cascading Style Sheets (CSS) implementation in Google Chrome before 16.0.912.63 on 64-bit platforms does not properly manage property arrays, which allows remote attackers to cause a denial of service (memory corruption) via unspecified 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 · high confidence

Google Chrome before 16.0.912.63 on 64-bit platforms contains a memory corruption vulnerability in its CSS implementation due to improper management of property arrays, which can be exploited remotely to cause denial of service.

MitigationUpdate Google Chrome to version 16.0.912.63 or later on all affected 64-bit 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
ChromeWeb browser
Affected:< 16.0.912.63
SafariWeb browser
Affected:< 5.1.4
ItunesApplication
Affected:< 10.6
Iphone OsOperating system
Affected:< 5.1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version and architecture
    Open Chrome, click menu > Help > About Google Chrome. Note the version number displayed. On Windows, right-click the Chrome shortcut and check Properties to see if it points to Program Files (64-bit) or Program Files (x86) (32-bit). On macOS, the System Information app shows if Chrome is 64-bit.
    Affected if Version is below 16.0.912.63 AND the browser is running as a 64-bit process
  2. Check Apple Safari version
    Open Safari, go to Safari menu > About Safari. Note the version number displayed.
    Affected if Version is below 5.1.4 and running on a 64-bit system
  3. Check Apple iTunes version
    Open iTunes, go to Help > About iTunes. Note the version number displayed.
    Affected if Version is below 10.6 on a 64-bit Windows system
  4. Check iOS version on iPhone
    On the iPhone, go to Settings > General > About. Note the Version number displayed.
    Affected if Version is below 5.1 on a 64-bit device (note: iOS 5.1 was 32-bit only, but the CVE specifically mentions 64-bit platforms)

You are affected if you are running any of these products in 64-bit mode with a version lower than the specified thresholds.

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 5.1 / 5.1.4 / 10.6 or later
Fixed in 5.15.1.410.6
Interim mitigation

Update Google Chrome to version 16.0.912.63 or later on all affected 64-bit systems.

Fix this in Chrome 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-3909 — 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-3909 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