security.snyk.io Open in urlscan Pro
2a02:26f0:480:5aa::ecd  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Developer Tools
 * Snyk Learn
 * Snyk Advisor
 * Code Checker

About Snyk
 1. Snyk Vulnerability Database
 2. npm
 3. jquery




CROSS-SITE SCRIPTING (XSS) AFFECTING JQUERY PACKAGE, VERSIONS <1.9.1

--------------------------------------------------------------------------------

SEVERITY

Recommended
5.4
medium
0
10

CVSS ASSESSMENT MADE BY SNYK'S SECURITY TEAM

Learn more


THREAT INTELLIGENCE


Exploit Maturity
Mature
EPSS
0.82% (83rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components
are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Cross-site Scripting (XSS) vulnerabilities in an interactive lesson.

Start learning
 * Snyk ID npm:jquery:20120206
 * published 20 Oct 2016
 * disclosed 19 Jun 2012
 * credit Richard Gibson

Report a new vulnerability Found a mistake?

INTRODUCED: 19 JUN 2012

CVE-2012-6708 Open this link in a new tab

CWE-79 Open this link in a new tab

Share



HOW TO FIX?

Upgrade jquery to version 1.9.1 or higher.


OVERVIEW

jquery is a package that makes things like HTML document traversal and
manipulation, event handling, animation, and Ajax much simpler with an
easy-to-use API that works across a multitude of browsers.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS).
The jQuery(strInput) function does not differentiate selectors from HTML in a
reliable fashion. In the vulnerable version, jQuery determined whether the input
was HTML or not by looking for the '<' character anywhere in the string, giving
attackers more flexibility when attempting to construct malicious payload.

In the fixed versions, jQuery only deems the input to be HTML if it explicitly
starts with '<', limiting exploitability only to attackers who can control the
beginning of a string, which is far less common.

Note: CVE-2017-16011 is a duplicate of CVE-2012-6708


DETAILS

A cross-site scripting attack occurs when the attacker tricks a legitimate
web-based application or site to accept a request as originating from a trusted
source.

This is done by escaping the context of the web application; the web application
then delivers that data to its users along with other trusted dynamic content,
without validating it. The browser unknowingly executes malicious script on the
client side (through client-side languages; usually JavaScript or HTML) in order
to perform actions that are otherwise typically blocked by the browser’s Same
Origin Policy.

ֿInjecting malicious code is the most prevalent manner by which XSS is
exploited; for this reason, escaping characters in order to prevent this
manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and
particularly key characters included in user input, to prevent those characters
from being interpreted in a dangerous context. For example, in HTML, < can be
coded as &lt; and > can be coded as &gt; in order to be interpreted and
displayed as themselves in text, while within the code itself, they are used for
HTML tags. If malicious content is injected into an application that escapes
special characters and that malicious content uses < and > as HTML tags, those
characters are nonetheless not interpreted as HTML tags by the browser if
they’ve been correctly escaped in the application code and in this way the
attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and
hijack user sessions, but XSS exploits have been used to expose sensitive
information, enable access to privileged services and functionality and deliver
malware.


TYPES OF ATTACKS

There are a few methods by which XSS can be manipulated:

Type Origin Description Stored Server The malicious code is inserted in the
application (usually as a link) by the attacker. The code is activated every
time a user clicks the link. Reflected Server The attacker delivers a malicious
link externally from the vulnerable web site application to a user. When
clicked, malicious code is sent to the vulnerable web site, which reflects the
attack back to the user’s browser. DOM-based Client The attacker forces the
user’s browser to render a malicious page. The data in the page itself delivers
the cross-site scripting data. Mutated The attacker injects code that appears
safe, but is then rewritten and modified by the browser, while parsing the
markup. An example is rebalancing unclosed quotation marks or even adding
quotation marks to unquoted parameters.


AFFECTED ENVIRONMENTS

The following environments are susceptible to an XSS attack:
 * Web servers
 * Application servers
 * Web application environments


HOW TO PREVENT

This section describes the top best practices designed to specifically protect
your code:
 * Sanitize data input in an HTTP request before reflecting it back, ensuring
   all data is validated, filtered or escaped before echoing anything back to
   the user, such as the values of query parameters during searches.
 * Convert special characters such as ?, &, /, <, > and spaces to their
   respective HTML or URL encoded equivalents.
 * Give users the option to disable client-side scripts.
 * Redirect invalid requests.
 * Detect simultaneous logins, including those from two separate IP addresses,
   and invalidate those sessions.
 * Use and enforce a Content Security Policy (source: Wikipedia) to disable any
   features that might be manipulated for an XSS attack.
 * Read the documentation for any of the libraries referenced in your code to
   understand which elements allow for embedded HTML.


REFERENCES

 * ExploitDB

 * GitHub Commit

 * JQuery Issue tracker

 * jsfiddle


CVSS SCORES

version 3.1
Expand this section


SNYK

5.4 medium
 * Attack Vector (AV)
   Network
 * Attack Complexity (AC)
   Low
 * Privileges Required (PR)
   None
 * User Interaction (UI)
   Required

 * Scope (S)
   Unchanged

 * Confidentiality (C)
   Low
 * Integrity (I)
   Low
 * Availability (A)
   None

Expand this section


SUSE

6.8 medium


PRODUCT

 * Snyk Open Source
 * Snyk Code
 * Snyk Container
 * Snyk Infrastructure as Code
 * Test with Github
 * Test with CLI


RESOURCES

 * Vulnerability DB
 * Documentation
 * Disclosed Vulnerabilities
 * Blog
 * FAQs


COMPANY

 * About
 * Jobs
 * Contact
 * Policies
 * Do Not Sell My Personal Information


CONTACT US

 * Support
 * Report a new vuln
 * Press Kit
 * Events


FIND US ONLINE

 * 
 * 
 * 
 * 


TRACK OUR DEVELOPMENT

 * 
 * 



© 2024 Snyk Limited

Registered in England and Wales. Company number: 09677925

Registered address: Highlands House, Basingstoke Road, Spencers Wood, Reading,
Berkshire, RG7 1NT.