Google » Chrome » 2.0.170.0 : Security Vulnerabilities Published In 2012 (Bypass)
Cpe Name:
cpe:/a:google:chrome:2.0.170.0
Copy Results
Download Results
Select Table
| # |
CVE ID
|
CWE ID
|
# of Exploits
|
Vulnerability Type(s)
|
Publish Date
|
Update Date
|
Score
|
Gained Access Level
|
Access
|
Complexity
|
Authentication
|
Conf.
|
Integ.
|
Avail.
|
|
1 |
CVE-2012-1846 |
264 |
|
Bypass |
2012-03-22 |
2012-08-13 |
10.0 |
None |
Remote |
Low |
Not required |
Complete |
Complete |
Complete |
|
Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the sandbox protection mechanism by leveraging access to a sandboxed process, as demonstrated by VUPEN during a Pwn2Own competition at CanSecWest 2012. NOTE: the primary affected product may be clarified later; it was not identified by the researcher, who reportedly stated "it really doesn't matter if it's third-party code." |
|
2 |
CVE-2012-1845 |
399 |
|
Exec Code Bypass |
2012-03-22 |
2012-08-13 |
10.0 |
None |
Remote |
Low |
Not required |
Complete |
Complete |
Complete |
|
Use-after-free vulnerability in Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the DEP and ASLR protection mechanisms, and execute arbitrary code, via unspecified vectors, as demonstrated by VUPEN during a Pwn2Own competition at CanSecWest 2012. NOTE: the primary affected product may be clarified later; it was not identified by the researcher, who reportedly stated "it really doesn't matter if it's third-party code." |
|
3 |
CVE-2011-3956 |
264 |
|
Bypass |
2012-02-08 |
2012-08-13 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
|
The extension implementation in Google Chrome before 17.0.963.46 does not properly handle sandboxed origins, which might allow remote attackers to bypass the Same Origin Policy via a crafted extension. |
|
4 |
CVE-2011-3080 |
362 |
|
Bypass |
2012-05-01 |
2012-08-13 |
7.5 |
None |
Remote |
Low |
Not required |
Partial |
Partial |
Partial |
|
Race condition in the Inter-process Communication (IPC) implementation in Google Chrome before 18.0.1025.168 allows attackers to bypass intended sandbox restrictions via unspecified vectors. |
|
5 |
CVE-2011-3072 |
264 |
|
Bypass |
2012-04-05 |
2013-02-14 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
|
Google Chrome before 18.0.1025.151 allows remote attackers to bypass the Same Origin Policy via vectors related to pop-up windows. |
|
6 |
CVE-2011-3067 |
264 |
|
Bypass |
2012-04-05 |
2013-02-14 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
|
Google Chrome before 18.0.1025.151 allows remote attackers to bypass the Same Origin Policy via vectors related to replacement of IFRAME elements. |
|
7 |
CVE-2011-3056 |
20 |
|
Bypass |
2012-03-22 |
2012-11-06 |
7.5 |
None |
Remote |
Low |
Not required |
Partial |
Partial |
Partial |
|
Google Chrome before 17.0.963.83 allows remote attackers to bypass the Same Origin Policy via vectors involving a "magic iframe." |
|
8 |
CVE-2011-3054 |
264 |
|
Bypass |
2012-03-22 |
2012-08-15 |
5.0 |
None |
Remote |
Low |
Not required |
None |
Partial |
None |
|
The WebUI privilege implementation in Google Chrome before 17.0.963.83 does not properly perform isolation, which allows remote attackers to bypass intended access restrictions via unspecified vectors. |
Total number of vulnerabilities :
8
Page :
1
(This Page)