CVE-2013-6632
published 2013-11-18CVE-2013-6632: Integer overflow in Google Chrome before 31.0.1650.57 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via…
PriorityP345critical9.3CVSS 2.0
AVNACMAuNCCICAC
EPSS
6.09%
92.7th percentile
Integer overflow in Google Chrome before 31.0.1650.57 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, as demonstrated during a Mobile Pwn2Own competition at PacSec 2013.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| chrome | < 31.0.1650.57 | 31.0.1650.57 | |
| chrome | <= 31.0.1650.57 | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-rc6h-cxrg-vv4c: Google Chrome before 31
ghsa_unreviewed·2022-05-14·CVSS 9.3
CVE-2013-6802 [CRITICAL] GHSA-rc6h-cxrg-vv4c: Google Chrome before 31
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.
GHSA
GHSA-grmv-75gc-629v: Integer overflow in Google Chrome before 31
ghsa_unreviewed·2022-05-14
CVE-2013-6632 [HIGH] GHSA-grmv-75gc-629v: Integer overflow in Google Chrome before 31
Integer overflow in Google Chrome before 31.0.1650.57 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, as demonstrated during a Mobile Pwn2Own competition at PacSec 2013.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://googlechromereleases.blogspot.com/2013/11/chrome-for-android-update.htmlhttp://googlechromereleases.blogspot.com/2013/11/stable-channel-update_14.htmlhttp://lists.opensuse.org/opensuse-security-announce/2013-11/msg00025.htmlhttp://lists.opensuse.org/opensuse-security-announce/2013-11/msg00026.htmlhttp://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.htmlhttp://lists.opensuse.org/opensuse-updates/2014-01/msg00042.htmlhttp://www.debian.org/security/2013/dsa-2799http://www.hppwn2own.com/chrome-nexus-4-samsung-galaxy-s4-falls/https://code.google.com/p/chromium/issues/detail?id=319117https://code.google.com/p/chromium/issues/detail?id=319125http://googlechromereleases.blogspot.com/2013/11/chrome-for-android-update.htmlhttp://googlechromereleases.blogspot.com/2013/11/stable-channel-update_14.htmlhttp://lists.opensuse.org/opensuse-security-announce/2013-11/msg00025.htmlhttp://lists.opensuse.org/opensuse-security-announce/2013-11/msg00026.htmlhttp://lists.opensuse.org/opensuse-security-announce/2013-12/msg00002.htmlhttp://lists.opensuse.org/opensuse-updates/2014-01/msg00042.htmlhttp://www.debian.org/security/2013/dsa-2799http://www.hppwn2own.com/chrome-nexus-4-samsung-galaxy-s4-falls/https://code.google.com/p/chromium/issues/detail?id=319117https://code.google.com/p/chromium/issues/detail?id=319125
2013-11-18
Published