ChromeWeb browser · Google
CVE-2011-3106
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 · uneditedThe WebSockets implementation in Google Chrome before 19.0.1084.52 does not properly handle use of SSL, which allows remote attackers to execute arbitrary code or 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 confidenceThe WebSockets implementation in Google Chrome before 19.0.1084.52 fails to properly handle SSL/TLS connections, leading to memory corruption. This memory corruption can be exploited by remote attackers to achieve arbitrary code execution or cause a denial of service.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Google Chrome installationOpen Chrome and navigate to chrome://version or click Help > About Google Chrome to view the installed version numberAffected if Google Chrome is not installed - the vulnerability does not apply
-
Verify the exact Chrome versionNote the full version string shown (e.g., 19.0.1084.51 or 19.0.1036.0) and compare it against the affected ranges: versions <= 19.0.1084.51, or exactly 19.0.1028.0 through 19.0.1036.3Affected if The installed version falls outside the affected list - the system is not vulnerable to this specific CVE
-
Confirm WebSockets usageInspect active network connections or application logs for WebSocket connections (ws:// or wss:// URLs), particularly secure WebSocket (wss://) connections that use SSL/TLSAffected if WebSockets with SSL/TLS (wss://) are actively in use - this is the specific configuration the vulnerability exploits
You are affected if Google Chrome versions 19.0.1028.0 through 19.0.1036.3 or any version <= 19.0.1084.51 are installed AND the browser is used to establish WebSocket connections over SSL/TLS (wss://).
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.
dbcve · scopedUpdate Google Chrome to version 19.0.1084.52 or later to remediate this vulnerability.
Chrome 19.0.1084.52 or later
- Check current Chrome version by navigating to chrome://settings/help or using the menu Help > About Google Chrome
- Update Chrome to the latest version. Chrome versions 19.0.1084.52 and later contain the fix for this vulnerability
- If auto-update is enabled, Chrome should automatically update; otherwise, download the latest version from the official Chrome download page
- Restart Chrome after the update completes
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
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 locallyCheck whether your project pulls in CVE-2011-3106 — 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-3106 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