First published: Tue Jan 28 2014(Updated: )
The StoreBuffer::ExemptPopularPages function in store-buffer.cc in Google V8 before 3.22.24.16, as used in Google Chrome before 32.0.1700.102, allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via vectors that trigger incorrect handling of "popular pages."
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Debian GNU/Linux | =7.0 | |
Debian GNU/Linux | =8.0 | |
Google Chrome | <=32.0.1700.101 | |
Google Chrome | =32.0.1700.0 | |
Google Chrome | =32.0.1700.2 | |
Google Chrome | =32.0.1700.3 | |
Google Chrome | =32.0.1700.4 | |
Google Chrome | =32.0.1700.5 | |
Google Chrome | =32.0.1700.6 | |
Google Chrome | =32.0.1700.7 | |
Google Chrome | =32.0.1700.8 | |
Google Chrome | =32.0.1700.9 | |
Google Chrome | =32.0.1700.10 | |
Google Chrome | =32.0.1700.11 | |
Google Chrome | =32.0.1700.12 | |
Google Chrome | =32.0.1700.13 | |
Google Chrome | =32.0.1700.14 | |
Google Chrome | =32.0.1700.15 | |
Google Chrome | =32.0.1700.16 | |
Google Chrome | =32.0.1700.17 | |
Google Chrome | =32.0.1700.18 | |
Google Chrome | =32.0.1700.19 | |
Google Chrome | =32.0.1700.21 | |
Google Chrome | =32.0.1700.22 | |
Google Chrome | =32.0.1700.23 | |
Google Chrome | =32.0.1700.24 | |
Google Chrome | =32.0.1700.26 | |
Google Chrome | =32.0.1700.27 | |
Google Chrome | =32.0.1700.28 | |
Google Chrome | =32.0.1700.29 | |
Google Chrome | =32.0.1700.30 | |
Google Chrome | =32.0.1700.31 | |
Google Chrome | =32.0.1700.32 | |
Google Chrome | =32.0.1700.33 | |
Google Chrome | =32.0.1700.34 | |
Google Chrome | =32.0.1700.35 | |
Google Chrome | =32.0.1700.38 | |
Google Chrome | =32.0.1700.39 | |
Google Chrome | =32.0.1700.41 | |
Google Chrome | =32.0.1700.50 | |
Google Chrome | =32.0.1700.51 | |
Google Chrome | =32.0.1700.52 | |
Google Chrome | =32.0.1700.53 | |
Google Chrome | =32.0.1700.54 | |
Google Chrome | =32.0.1700.55 | |
Google Chrome | =32.0.1700.56 | |
Google Chrome | =32.0.1700.57 | |
Google Chrome | =32.0.1700.58 | |
Google Chrome | =32.0.1700.59 | |
Google Chrome | =32.0.1700.62 | |
Google Chrome | =32.0.1700.63 | |
Google Chrome | =32.0.1700.64 | |
Google Chrome | =32.0.1700.65 | |
Google Chrome | =32.0.1700.66 | |
Google Chrome | =32.0.1700.67 | |
Google Chrome | =32.0.1700.68 | |
Google Chrome | =32.0.1700.69 | |
Google Chrome | =32.0.1700.70 | |
Google Chrome | =32.0.1700.71 | |
Google Chrome | =32.0.1700.72 | |
Google Chrome | =32.0.1700.74 | |
Google Chrome | =32.0.1700.75 | |
Google Chrome | =32.0.1700.76 | |
Google Chrome | =32.0.1700.77 | |
Google Chrome | =32.0.1700.94 | |
Google Chrome | =32.0.1700.95 | |
Google Chrome | =32.0.1700.96 | |
Google Chrome | =32.0.1700.97 | |
Google Chrome | =32.0.1700.98 | |
Google Chrome | =32.0.1700.99 | |
Google Chrome | =32.0.1700.100 | |
openSUSE | =12.3 | |
openSUSE | =13.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-6650 has a severity rating that indicates it can lead to denial of service or memory corruption.
To fix CVE-2013-6650, update Google Chrome to version 32.0.1700.102 or later.
CVE-2013-6650 affects Google Chrome versions prior to 32.0.1700.102.
CVE-2013-6650 can be exploited by remote attackers to cause memory corruption and potential denial of service.
While CVE-2013-6650 specifically affects Google Chrome, it also impacts certain versions of Debian Linux.