ChromeWeb browser · Google
CVE-2011-3913
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 · uneditedUse-after-free vulnerability in Google Chrome before 16.0.912.63 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to Range handling.
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 confidenceA use-after-free vulnerability in Google Chrome versions before 16.0.912.63 exists in the Range handling component. This memory corruption issue can be exploited remotely through specially crafted web content, potentially allowing attackers to cause a denial of service or achieve unspecified code execution.
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
< 16.0.912.63
SafariWeb browser
< 6.0< 10.7< 6.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Google Chrome versionNavigate to Chrome menu > Help > About Google Chrome, or visit chrome://version/ in the address bar. Note the version number displayed.Affected if The displayed version is earlier than 16.0.912.63
-
Identify installed Apple Safari versionOpen Safari > Safari menu > About Safari, or check /Applications/Safari.app/Contents/Info.plist for CFBundleShortVersionString.Affected if The displayed version is earlier than 6.0 (e.g., 5.x)
-
Identify installed Apple iTunes versionOpen iTunes > Help > About iTunes, or check the version displayed in the iTunes window header.Affected if The displayed version is earlier than 10.7
-
Identify iOS version on Apple deviceOn the device, go to Settings > General > About > Version. For iTunes-synced devices, check in iTunes device Summary page.Affected if The displayed version is earlier than 6.0 (e.g., 5.x)
-
Confirm vulnerability trigger conditionThe vulnerability is triggered through the Range handling component when processing specially crafted web content. Users who browse untrusted websites are potentially affected if their version is vulnerable.Affected if A vulnerable browser version is in use AND the user accesses web content that exploits the Range use-after-free flaw
A user is affected if they have any of the following installed: Google Chrome < 16.0.912.63, Safari < 6.0, iTunes < 10.7, or iOS < 6.0, and they access web content that exploits the Range handling component.
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 data6.010.716.0.912.63
Update Google Chrome to version 16.0.912.63 or later to remediate this vulnerability. Organizations should ensure automated browser update mechanisms are enabled or deploy the patched version enterprise-wide.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3913 — 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-3913 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