CVE-2012-5851: XSS
First published: Thu Nov 15 2012(Updated: )
html/parser/XSSAuditor.cpp in WebCore in WebKit, as used in Google Chrome through 22 and Safari 5.1.7, does not consider all possible output contexts of reflected data, which makes it easier for remote attackers to bypass a cross-site scripting (XSS) protection mechanism via a crafted string, aka rdar problem 12019108.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| WebKit | ||
| Google Chrome (Trace Event) | <=22.0.1229.96 | |
| Google Chrome (Trace Event) | =22.0.1229.0 | |
| Google Chrome (Trace Event) | =22.0.1229.1 | |
| Google Chrome (Trace Event) | =22.0.1229.2 | |
| Google Chrome (Trace Event) | =22.0.1229.3 | |
| Google Chrome (Trace Event) | =22.0.1229.4 | |
| Google Chrome (Trace Event) | =22.0.1229.6 | |
| Google Chrome (Trace Event) | =22.0.1229.7 | |
| Google Chrome (Trace Event) | =22.0.1229.8 | |
| Google Chrome (Trace Event) | =22.0.1229.9 | |
| Google Chrome (Trace Event) | =22.0.1229.10 | |
| Google Chrome (Trace Event) | =22.0.1229.11 | |
| Google Chrome (Trace Event) | =22.0.1229.12 | |
| Google Chrome (Trace Event) | =22.0.1229.14 | |
| Google Chrome (Trace Event) | =22.0.1229.16 | |
| Google Chrome (Trace Event) | =22.0.1229.17 | |
| Google Chrome (Trace Event) | =22.0.1229.18 | |
| Google Chrome (Trace Event) | =22.0.1229.20 | |
| Google Chrome (Trace Event) | =22.0.1229.21 | |
| Google Chrome (Trace Event) | =22.0.1229.22 | |
| Google Chrome (Trace Event) | =22.0.1229.23 | |
| Google Chrome (Trace Event) | =22.0.1229.24 | |
| Google Chrome (Trace Event) | =22.0.1229.25 | |
| Google Chrome (Trace Event) | =22.0.1229.26 | |
| Google Chrome (Trace Event) | =22.0.1229.27 | |
| Google Chrome (Trace Event) | =22.0.1229.28 | |
| Google Chrome (Trace Event) | =22.0.1229.29 | |
| Google Chrome (Trace Event) | =22.0.1229.31 | |
| Google Chrome (Trace Event) | =22.0.1229.32 | |
| Google Chrome (Trace Event) | =22.0.1229.33 | |
| Google Chrome (Trace Event) | =22.0.1229.35 | |
| Google Chrome (Trace Event) | =22.0.1229.36 | |
| Google Chrome (Trace Event) | =22.0.1229.37 | |
| Google Chrome (Trace Event) | =22.0.1229.39 | |
| Google Chrome (Trace Event) | =22.0.1229.48 | |
| Google Chrome (Trace Event) | =22.0.1229.49 | |
| Google Chrome (Trace Event) | =22.0.1229.50 | |
| Google Chrome (Trace Event) | =22.0.1229.51 | |
| Google Chrome (Trace Event) | =22.0.1229.52 | |
| Google Chrome (Trace Event) | =22.0.1229.53 | |
| Google Chrome (Trace Event) | =22.0.1229.54 | |
| Google Chrome (Trace Event) | =22.0.1229.55 | |
| Google Chrome (Trace Event) | =22.0.1229.56 | |
| Google Chrome (Trace Event) | =22.0.1229.57 | |
| Google Chrome (Trace Event) | =22.0.1229.58 | |
| Google Chrome (Trace Event) | =22.0.1229.59 | |
| Google Chrome (Trace Event) | =22.0.1229.60 | |
| Google Chrome (Trace Event) | =22.0.1229.62 | |
| Google Chrome (Trace Event) | =22.0.1229.63 | |
| Google Chrome (Trace Event) | =22.0.1229.64 | |
| Google Chrome (Trace Event) | =22.0.1229.65 | |
| Google Chrome (Trace Event) | =22.0.1229.67 | |
| Google Chrome (Trace Event) | =22.0.1229.76 | |
| Google Chrome (Trace Event) | =22.0.1229.78 | |
| Google Chrome (Trace Event) | =22.0.1229.79 | |
| Google Chrome (Trace Event) | =22.0.1229.89 | |
| Google Chrome (Trace Event) | =22.0.1229.91 | |
| Google Chrome (Trace Event) | =22.0.1229.92 | |
| Google Chrome (Trace Event) | =22.0.1229.94 | |
| Google Chrome (Trace Event) | =22.0.1229.95 | |
| Apple Mobile Safari | =5.1.7 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2012-5851?
CVE-2012-5851 is rated as a medium severity vulnerability.
How do I fix CVE-2012-5851?
To fix CVE-2012-5851, update your Google Chrome or Apple Safari to the latest version.
Which software is affected by CVE-2012-5851?
CVE-2012-5851 affects WebKit as used in Google Chrome through version 22 and Apple Safari version 5.1.7.
What type of attack does CVE-2012-5851 facilitate?
CVE-2012-5851 makes it easier for remote attackers to bypass cross-site scripting (XSS) protection mechanisms.
Is CVE-2012-5851 a user-exploitable vulnerability?
Yes, CVE-2012-5851 is potentially exploitable by users visiting specially crafted web pages.
- agent/type
- agent/references
- agent/author
- agent/severity
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/source
- agent/weakness
- agent/tags
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/apple
- canonical/webkit
- vendor/google
- canonical/google chrome (trace event)
- version/google chrome (trace event)/22.0.1229.96
- version/google chrome (trace event)/22.0.1229.0
- version/google chrome (trace event)/22.0.1229.1
- version/google chrome (trace event)/22.0.1229.2
- version/google chrome (trace event)/22.0.1229.3
- version/google chrome (trace event)/22.0.1229.4
- version/google chrome (trace event)/22.0.1229.6
- version/google chrome (trace event)/22.0.1229.7
- version/google chrome (trace event)/22.0.1229.8
- version/google chrome (trace event)/22.0.1229.9
- version/google chrome (trace event)/22.0.1229.10
- version/google chrome (trace event)/22.0.1229.11
- version/google chrome (trace event)/22.0.1229.12
- version/google chrome (trace event)/22.0.1229.14
- version/google chrome (trace event)/22.0.1229.16
- version/google chrome (trace event)/22.0.1229.17
- version/google chrome (trace event)/22.0.1229.18
- version/google chrome (trace event)/22.0.1229.20
- version/google chrome (trace event)/22.0.1229.21
- version/google chrome (trace event)/22.0.1229.22
- version/google chrome (trace event)/22.0.1229.23
- version/google chrome (trace event)/22.0.1229.24
- version/google chrome (trace event)/22.0.1229.25
- version/google chrome (trace event)/22.0.1229.26
- version/google chrome (trace event)/22.0.1229.27
- version/google chrome (trace event)/22.0.1229.28
- version/google chrome (trace event)/22.0.1229.29
- version/google chrome (trace event)/22.0.1229.31
- version/google chrome (trace event)/22.0.1229.32
- version/google chrome (trace event)/22.0.1229.33
- version/google chrome (trace event)/22.0.1229.35
- version/google chrome (trace event)/22.0.1229.36
- version/google chrome (trace event)/22.0.1229.37
- version/google chrome (trace event)/22.0.1229.39
- version/google chrome (trace event)/22.0.1229.48
- version/google chrome (trace event)/22.0.1229.49
- version/google chrome (trace event)/22.0.1229.50
- version/google chrome (trace event)/22.0.1229.51
- version/google chrome (trace event)/22.0.1229.52
- version/google chrome (trace event)/22.0.1229.53
- version/google chrome (trace event)/22.0.1229.54
- version/google chrome (trace event)/22.0.1229.55
- version/google chrome (trace event)/22.0.1229.56
- version/google chrome (trace event)/22.0.1229.57
- version/google chrome (trace event)/22.0.1229.58
- version/google chrome (trace event)/22.0.1229.59
- version/google chrome (trace event)/22.0.1229.60
- version/google chrome (trace event)/22.0.1229.62
- version/google chrome (trace event)/22.0.1229.63
- version/google chrome (trace event)/22.0.1229.64
- version/google chrome (trace event)/22.0.1229.65
- version/google chrome (trace event)/22.0.1229.67
- version/google chrome (trace event)/22.0.1229.76
- version/google chrome (trace event)/22.0.1229.78
- version/google chrome (trace event)/22.0.1229.79
- version/google chrome (trace event)/22.0.1229.89
- version/google chrome (trace event)/22.0.1229.91
- version/google chrome (trace event)/22.0.1229.92
- version/google chrome (trace event)/22.0.1229.94
- version/google chrome (trace event)/22.0.1229.95
- canonical/apple mobile safari
- version/apple mobile safari/5.1.7