CVE-2013-6802
Summary
| CVE | CVE-2013-6802 |
|---|---|
| State | PUBLISHED |
| Assigner | mitre |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2013-11-18 05:23:57 UTC |
| Updated | 2026-04-29 01:13:23 UTC |
| Description | Google Chrome before 31.0.1650.57 allows remote attackers to bypass intended sandbox restrictions by leveraging access to a renderer process, as demonstrated during a Mobile Pwn2Own competition at PacSec 2013, a different vulnerability than CVE-2013-6632. |
Risk And Classification
Primary CVSS: v2.0 5.8 from [email protected]
AV:N/AC:M/Au:N/C:P/I:P/A:N
EPSS: 0.003790000 probability, percentile 0.593920000 (date 2026-04-29)
Problem Types: CWE-264 | n/a
CVSS v2.0 Breakdown
Access Vector
NetworkAccess Complexity
MediumAuthentication
NoneConfidentiality
PartialIntegrity
PartialAvailability
NoneAV:N/AC:M/Au:N/C:P/I:P/A:N
NVD Known Affected Configurations (CPE 2.3)
Vendor Declared Affected Products
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Sign in - Google Accounts | af854a3a-2127-422b-91ae-364da2661108 | code.google.com | Vendor Advisory |
| IBM X-Force Exchange | af854a3a-2127-422b-91ae-364da2661108 | exchange.xforce.ibmcloud.com | Third Party Advisory, VDB Entry |
| Chrome Releases: Stable Channel Update | af854a3a-2127-422b-91ae-364da2661108 | googlechromereleases.blogspot.com | Patch, Vendor Advisory |
| 319117 - chromium - An open-source project to help move the web forward. - Monorail | af854a3a-2127-422b-91ae-364da2661108 | code.google.com | Vendor Advisory |
| Chrome on a Nexus 4 and Samsung Galaxy S4 falls - PWN2OWN | af854a3a-2127-422b-91ae-364da2661108 | www.hppwn2own.com | Third Party Advisory |
| Chrome Releases: Chrome for Android Update | af854a3a-2127-422b-91ae-364da2661108 | googlechromereleases.blogspot.com | Patch, Vendor Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.