ChromeWeb browser · Google
CVE-2011-3111
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 · uneditedGoogle V8, as used in Google Chrome before 19.0.1084.52, allows remote attackers to cause a denial of service (invalid read operation) 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 · moderate confidenceThis is a memory safety vulnerability in Google V8 JavaScript engine (used in Chrome prior to version 19.0.1084.52) that allows remote attackers to cause a denial of service via an invalid read operation. The vulnerability stems from an out-of-bounds memory read in the V8 engine when processing unspecified malicious input.
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.51= 19.0.1028.0= 19.0.1029.0= 19.0.1030.0= 19.0.1031.0= 19.0.1032.0= 19.0.1033.0= 19.0.1034.0= 19.0.1035.0= 19.0.1036.0= 19.0.1036.2= 19.0.1036.3CVSS 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.
-
Find installed Chrome versionOpen chrome://version in the Chrome address bar and note the version number, or run 'chrome --version' or 'google-chrome --version' from command lineAffected if Version is 19.0.1084.51 or lower, or exactly matches any of these: 19.0.1028.0, 19.0.1029.0, 19.0.1030.0, 19.0.1031.0, 19.0.1032.0, 19.0.1033.0, 19.0.1034.0, 19.0.1035.0, 19.0.1036.0, 19.0.1036.2, 19.0.1036.3
-
Verify V8 JavaScript engine is presentNavigate to chrome://version and check the Command Line field for entries containing 'V8' or navigate to chrome://settings and verify JavaScript is enabled under Privacy and security settingsAffected if V8 is disabled (unusual for Chrome) - the vulnerability only applies when V8 processes JavaScript, which is the default and required state
-
Confirm Chrome is the affected productVerify the browser is Google Chrome (not Chromium or another Chromium-based browser) by checking chrome://version for the 'Product' fieldAffected if Product name is not Google Chrome - the CVE specifically targets Google Chrome, not upstream Chromium
You are affected if your Google Chrome version is 19.0.1084.51 or lower, or exactly matches any of the specific versions 19.0.1028.0 through 19.0.1036.3 listed in the affected products.
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 dataUpdate Google Chrome to version 19.0.1084.52 or later, or ensure all deployed Chrome instances receive the relevant security patch through standard patch management processes.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3111 — 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-3111 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