CVE-2011-3106
Last modified
CVE-2011-3106 is a vulnerability of currently unknown severity. The 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.. EPSS estimates a 4.27% chance of exploitation in the next 30 days.
Description
The 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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Chrome | <= 19.0.1084.51 | |
| Chrome | 19.0.1028.0 | |
| Chrome | 19.0.1029.0 | |
| Chrome | 19.0.1030.0 | |
| Chrome | 19.0.1031.0 | |
| Chrome | 19.0.1032.0 | |
| Chrome | 19.0.1033.0 | |
| Chrome | 19.0.1034.0 | |
| Chrome | 19.0.1035.0 | |
| Chrome | 19.0.1036.0 | |
| Chrome | 19.0.1036.2 | |
| Chrome | 19.0.1036.3 | |
| Chrome | 19.0.1036.4 | |
| Chrome | 19.0.1036.6 | |
| Chrome | 19.0.1036.7 | |
| Chrome | 19.0.1037.0 | |
| Chrome | 19.0.1038.0 | |
| Chrome | 19.0.1039.0 | |
| Chrome | 19.0.1040.0 | |
| Chrome | 19.0.1041.0 | |
| Chrome | 19.0.1042.0 | |
| Chrome | 19.0.1043.0 | |
| Chrome | 19.0.1044.0 | |
| Chrome | 19.0.1045.0 | |
| Chrome | 19.0.1046.0 | |
| Chrome | 19.0.1047.0 | |
| Chrome | 19.0.1048.0 | |
| Chrome | 19.0.1049.0 | |
| Chrome | 19.0.1049.1 | |
| Chrome | 19.0.1049.2 | |
| Chrome | 19.0.1049.3 | |
| Chrome | 19.0.1050.0 | |
| Chrome | 19.0.1051.0 | |
| Chrome | 19.0.1052.0 | |
| Chrome | 19.0.1053.0 | |
| Chrome | 19.0.1054.0 | |
| Chrome | 19.0.1055.0 | |
| Chrome | 19.0.1055.1 | |
| Chrome | 19.0.1055.2 | |
| Chrome | 19.0.1055.3 | |
| Chrome | 19.0.1056.0 | |
| Chrome | 19.0.1056.1 | |
| Chrome | 19.0.1057.0 | |
| Chrome | 19.0.1057.1 | |
| Chrome | 19.0.1057.3 | |
| Chrome | 19.0.1058.0 | |
| Chrome | 19.0.1058.1 | |
| Chrome | 19.0.1059.0 | |
| Chrome | 19.0.1060.0 | |
| Chrome | 19.0.1060.1 |
Showing 50 of 132 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2011-3106?
How severe is CVE-2011-3106?
How do I fix CVE-2011-3106?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2011
- CVE-2011-3100Google Chrome before 19.0.1084.46 does not properly draw das…
- CVE-2011-3101Google Chrome before 19.0.1084.46 on Linux does not properly…
- CVE-2011-3102Off-by-one error in libxml2, as used in Google Chrome before…
- CVE-2011-3103Google V8, as used in Google Chrome before 19.0.1084.52, doe…
- CVE-2011-3104Skia, as used in Google Chrome before 19.0.1084.52, allows r…
- CVE-2011-3105Use-after-free vulnerability in the Cascading Style Sheets (…
- CVE-2011-3107Google Chrome before 19.0.1084.52 does not properly implemen…
- CVE-2011-3108Use-after-free vulnerability in Google Chrome before 19.0.10…
- CVE-2011-3109Google Chrome before 19.0.1084.52 on Linux does not properly…
- CVE-2011-3110The PDF functionality in Google Chrome before 19.0.1084.52 a…
- CVE-2011-3111Google V8, as used in Google Chrome before 19.0.1084.52, all…
- CVE-2011-3112Use-after-free vulnerability in the PDF functionality in Goo…
Are you affected by CVE-2011-3106?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
