First published: Fri Aug 31 2012(Updated: )
Google Chrome before 21.0.1180.89 does not properly perform line breaking, which allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted document.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
SUSE Linux | =12.1 | |
SUSE Linux | =12.2 | |
Google Chrome (Trace Event) | <=21.0.1180.88 | |
Google Chrome (Trace Event) | =21.0.1180.0 | |
Google Chrome (Trace Event) | =21.0.1180.1 | |
Google Chrome (Trace Event) | =21.0.1180.2 | |
Google Chrome (Trace Event) | =21.0.1180.31 | |
Google Chrome (Trace Event) | =21.0.1180.32 | |
Google Chrome (Trace Event) | =21.0.1180.33 | |
Google Chrome (Trace Event) | =21.0.1180.34 | |
Google Chrome (Trace Event) | =21.0.1180.35 | |
Google Chrome (Trace Event) | =21.0.1180.36 | |
Google Chrome (Trace Event) | =21.0.1180.37 | |
Google Chrome (Trace Event) | =21.0.1180.38 | |
Google Chrome (Trace Event) | =21.0.1180.39 | |
Google Chrome (Trace Event) | =21.0.1180.41 | |
Google Chrome (Trace Event) | =21.0.1180.46 | |
Google Chrome (Trace Event) | =21.0.1180.47 | |
Google Chrome (Trace Event) | =21.0.1180.48 | |
Google Chrome (Trace Event) | =21.0.1180.49 | |
Google Chrome (Trace Event) | =21.0.1180.50 | |
Google Chrome (Trace Event) | =21.0.1180.51 | |
Google Chrome (Trace Event) | =21.0.1180.52 | |
Google Chrome (Trace Event) | =21.0.1180.53 | |
Google Chrome (Trace Event) | =21.0.1180.54 | |
Google Chrome (Trace Event) | =21.0.1180.55 | |
Google Chrome (Trace Event) | =21.0.1180.56 | |
Google Chrome (Trace Event) | =21.0.1180.57 | |
Google Chrome (Trace Event) | =21.0.1180.59 | |
Google Chrome (Trace Event) | =21.0.1180.60 | |
Google Chrome (Trace Event) | =21.0.1180.61 | |
Google Chrome (Trace Event) | =21.0.1180.62 | |
Google Chrome (Trace Event) | =21.0.1180.63 | |
Google Chrome (Trace Event) | =21.0.1180.64 | |
Google Chrome (Trace Event) | =21.0.1180.68 | |
Google Chrome (Trace Event) | =21.0.1180.69 | |
Google Chrome (Trace Event) | =21.0.1180.70 | |
Google Chrome (Trace Event) | =21.0.1180.71 | |
Google Chrome (Trace Event) | =21.0.1180.72 | |
Google Chrome (Trace Event) | =21.0.1180.73 | |
Google Chrome (Trace Event) | =21.0.1180.74 | |
Google Chrome (Trace Event) | =21.0.1180.75 | |
Google Chrome (Trace Event) | =21.0.1180.76 | |
Google Chrome (Trace Event) | =21.0.1180.77 | |
Google Chrome (Trace Event) | =21.0.1180.78 | |
Google Chrome (Trace Event) | =21.0.1180.79 | |
Google Chrome (Trace Event) | =21.0.1180.80 | |
Google Chrome (Trace Event) | =21.0.1180.81 | |
Google Chrome (Trace Event) | =21.0.1180.82 | |
Google Chrome (Trace Event) | =21.0.1180.83 | |
Google Chrome (Trace Event) | =21.0.1180.84 | |
Google Chrome (Trace Event) | =21.0.1180.85 | |
Google Chrome (Trace Event) | =21.0.1180.86 | |
Google Chrome (Trace Event) | =21.0.1180.87 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2012-2865 has a severity that allows for denial of service due to an out-of-bounds read in Google Chrome.
To fix CVE-2012-2865, update Google Chrome to version 21.0.1180.89 or later.
CVE-2012-2865 affects Google Chrome versions prior to 21.0.1180.89.
Yes, CVE-2012-2865 can be exploited by remote attackers through crafted documents.
CVE-2012-2865 primarily affects Google Chrome regardless of the operating system it runs on.