Cross-Site Scripting in jquery
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| jquery npm |
|
|
| org.webjars.npm:jquery Maven |
|
|
| jQuery NuGet |
|
| Product | Affected | Fixed in |
|---|---|---|
| jquery npm |
|
|
| org.webjars.npm:jquery Maven |
|
|
| jQuery NuGet |
|
|
| jquery-rails RubyGems |
|
|
jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common.
From the CVE record · mitre
In affected versions, jQuery(strInput) can mistake a selector containing '<' for HTML. An attacker who can control input passed to this function may be able to cause cross-site scripting; the input does not specify authentication or user-interaction requirements.
Check applications using npm jquery, Maven org.webjars.npm:jquery, or NuGet jQuery before 1.9.0, or RubyGems jquery-rails before 2.2.0.