|3 via 4 paths|
Find, fix and prevent vulnerabilities in your code.
- Vulnerable module: graphiql
- Introduced through: firstname.lastname@example.org
Introduced through: email@example.comRemediation: Upgrade to firstname.lastname@example.org.
graphiql is a graphical interactive in-browser GraphQL IDE.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS). This package is vulnerable to compromised HTTP schema introspection responses or schema prop values with malicious GraphQL type names, exposing a dynamic XSS attack surface that can allow code injection on operation autocomplete. In order for the attack to take place, the user must load a vulnerable schema in
graphiql. There are a number of ways that can occur.
By default, the schema URL is not attacker-controllable in
graphiql or in its suggested implementations or examples, leaving only very complex attack vectors. If a custom implementation of
graphiql's fetcher allows the schema URL to be set dynamically, such as a URL query parameter like
?endpoint= in graphql-playground, or a database provided value, then this custom
graphiql implementation is vulnerable to phishing attacks, and thus much more readily available, low or no privilege level XSS attacks. The URLs could look like any generic looking graphql schema URL.
It should be noted that desktop clients such as Altair, Insomnia, Postwoman, do not appear to be impacted by this. This vulnerability does not impact codemirror-graphql, monaco-graphql or other dependents, as it exists in
onHasCompletion.ts in graphiql. It does impact all forks of graphiql, and every released version of graphiql.
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.
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
> can be coded as
> 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
> 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:
|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.|
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.
graphiql to version 1.4.7 or higher.
- Vulnerable module: node-fetch
- Introduced through: email@example.com
Introduced through: firstname.lastname@example.org › email@example.com › firstname.lastname@example.org › email@example.com › firstname.lastname@example.org › email@example.com › firstname.lastname@example.orgRemediation: Upgrade to email@example.com.
Introduced through: firstname.lastname@example.org › email@example.com › firstname.lastname@example.org › email@example.com › firstname.lastname@example.org › email@example.com › firstname.lastname@example.org › email@example.comRemediation: Upgrade to firstname.lastname@example.org.
node-fetch is an A light-weight module that brings window.fetch to node.js
Affected versions of this package are vulnerable to Denial of Service. Node Fetch did not honor the
size option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure.
node-fetch to version 2.6.1, 3.0.0-beta.9 or higher.
- Vulnerable module: markdown-it
- Introduced through: email@example.com
Introduced through: firstname.lastname@example.org › email@example.comRemediation: Upgrade to firstname.lastname@example.org.
markdown-it is a modern pluggable markdown parser.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). Parsing __*_… takes quadratic time, this could be a denial of service vulnerability in an application that parses user input.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
AThe string must start with the letter 'A'
(B|C+)+The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the
+matches one or more times). The
+at the end of this section states that we can look for one or more matches of this section.
DFinally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as
It most cases, it doesn't take very long for a regex engine to find a match:
From there, the number of steps the engine must use to validate a string just continues to grow.
|String||Number of C's||Number of steps|
markdown-it to version 10.0.0 or higher.