[Snyk] Security upgrade documentation from 4.0.0 to 12.1.3

[harunpehlivan]

This PR was automatically created by Snyk using the credentials of a real user.

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • packages/gatsby-transformer-documentationjs/package.json

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	663/1000 Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 5.4	Cross-site Scripting (XSS) SNYK-JS-PARSEURL-2942134	Yes	Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: documentation

The new version differs by 250 commits.

• 6b9e5ce chore(release): 12.1.3
• 344e804 fix: upgrade git-url-parse to fix a parsing issue ([1.0] Throw error and quit if there's a JS parse error for gatsby-config.js fixes #1290 gatsbyjs/gatsby#1296)
• 6e62982 Add homepage to package.json (Accessing PropTypes via the main React package is deprecated gatsbyjs/gatsby#1282)
• d5b5e3c Update CODE_OF_CONDUCT.md (gatsby-config.js syntax errors can silently fail gatsbyjs/gatsby#1290)
• c1e4dbe Update RECIPES.md (Added blog post on <img/> tags gatsbyjs/gatsby#1291)
• 3506ef2 Fix beacuse typo ([1.0][gatsby-plugin-glamor] Fix typo gatsbyjs/gatsby#1292)
• bbc988e Patch 11 ([1.0][using-remark] Don't import from gatsby-config gatsbyjs/gatsby#1289)
• 3ecc358 HTTPS link to https://eslint.org/docs/rules/valid-jsdoc.html ([1.0] Add eslint-loader including eslint-plugin-graphql gatsbyjs/gatsby#1287)
• acf3cfb fix filenames typo ([1.0] [gatsby-source-contentful] WIP support creating localized nodes gatsbyjs/gatsby#1279)
• e7da906 HTTPS link to daringfireball.net ([1.0] Scan for graphl queries in locations other than src.  gatsbyjs/gatsby#1280)
• 635e52e chore(release): 12.1.2
• 3e0958b fix: check for empty diff ([1.0] Update feed-plugin README gatsbyjs/gatsby#1273)
• 1548574 Fix a crash in ts_doctrine.js (Don't use the sass loader on build-javascript gatsbyjs/gatsby#1278)
• b2c3175 editorconfig rules should apply to CSS too ([1.0][using-remark] Remove console.log gatsbyjs/gatsby#1275)
• 29c19ff chore(release): 12.1.1
• 27a29be fix: Git submodule support for repo names with a dot ([1.0] gatsby-plugin-sitemap does not work gatsbyjs/gatsby#1271)
• 43cd57d chore(release): 12.1.0
• ec36b41 feat: Add git submodules support to github linking ([1.0] Upgrade Prettier to 1.5 gatsbyjs/gatsby#1270)
• a1a2310 chore(release): 12.0.3
• f9039e9 fix: Allow skipped array arguments in destructuring. Fixes [Snyk] Security upgrade gatsby-transformer-remark from 1.7.44 to 5.25.1 #1247 (Use localized space gatsbyjs/gatsby#1266)
• 4d99385 chore(release): 12.0.2
• 226a666 deps: Remove unmaintained dependency: disparity ([1.0] [source-contentful] Create new way to detect not-resolvable entries/assets gatsbyjs/gatsby#1264)
• 798d32e chore(release): 12.0.1
• 821a15e fix: Crash when called with no inputs. yargs now variadic positional arguments undefined instead of []

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

[secureflag-knowledge-base]

Cross-Site Scripting

Click here to find a Cross-Site Scripting training lab

Description

Cross-Site Scripting (otherwise known as XSS) is a vulnerability that allows a malicious actor to manipulate a legitimate user's interactions with a vulnerable web application. Attackers exploit this to bypass the same-origin policy, often allowing them to perform any actions that the target user would normally perform, including gaining access to their data. In cases where the victim user has privileged application access, the attacker may use XSS to seize control of the application.

XSS attacks typically occur in web applications when data is received, frequently in the form of a web request, and the data is reflected back in the HTTP response to the user without validation.

XSS attacks can generally be divided into the following three categories.

#

Read more

Reflected XSS

Reflected XSS attacks arise when a web server reflects injected script, such as a search result, an error message, or any other response that includes some or all of the input sent to the server as part of the request.

The attack is then delivered to the victim through another route (e.g., e-mail or an alternative website), thus tricking the user into clicking on a malicious link. The injected code travels to the vulnerable website, which reflects the attack payload back to the user's browser. The browser then executes the code because it came from a "trusted" server.

Stored XSS

In the Stored XSS attack, the injected script is stored on the target application as legitimate content, such as a message in a forum or a comment in a blog post. The injected code is stored in the database and sent to the users when it is retrieved, thus executing the attack payload in the victim's browser.

Dom-based XSS

DOM-based XSS vulnerabilities usually occur when the JavaScript in a page takes user-provided data from a source in the HTML, such as the document.location, and passes it to a JavaScript function that allows JavaScript code to be run, such as innerHTML(). The classic attack delivers the payload to the victim through another route (e.g., e-mail or an alternative website) and thus tricks the user into visiting a malicious link. The exploitation is client-side, and the code is immediately executed in the user's browser.

Impact

XSS attacks can result in the disclosure of the user's session cookie, allowing an attacker to hijack the user's session and take over the account. Even though HTTPOnly is used to protect cookies, an attacker can still execute actions on behalf of the user in the context of the affected website.

As with all of the severe vulnerabilities that make up a part of the OWASP Top 10, XSS attacks can result in the complete compromise of a user's system. As stated in the description, if an attacker compromises a user holding the 'keys to the kingdom,' i.e., privileged access to applications/administrator rights, the results can be devastating.

Prevention

XSS attacks can be mitigated by performing appropriate server-side validation and escaping. Remediation relies on performing Output Encoding (e.g., using an escape syntax) for the type of HTML context into which untrusted data is reflected.

Input Validation

• Exact Match: Only accept values from a finite list of known values.
• Allow list: If a list of all the possible values can't be created, accept only known good data and reject all unexpected input.
• Deny list: If an allow-list approach is not feasible (on free form text areas, for example), reject all known bad values.

Output Encoding

Output Encoding is used to convert untrusted input into a safe form where the input is displayed as data to the user without executing as code in the browser. Output Encoding is performed when the data leaves the application to a downstream component. The table below lists the possible downstream contexts where the untrusted input could be used:

Context	Code	Encoding
HTML Body	<div>USER-CONTROLLED-DATA</div>	HTML Encoding
HTML Attribute	<input type="text" value="USER-CONTROLLED-DATA">	HTML Attribute Encoding
URL Parameter	<a href="/search?value=USER-CONTROLLED-DATA">Search</a>	URL Encoding
CSS	<div style="width: USER-CONTROLLED-DATA;">Selection</div>	CSS Hex Encoding
JavaScript	<script>var lang ='USER-CONTROLLED-DATA';</script> <script>setLanguage('USER-CONTROLLED-DATA');</script>	JavaScript Encoding

The following chart details a list of critical output encoding methods required to mitigate Cross-Site Scripting:

Encoding Type	Encoding Mechanism
HTML Entity Encoding	Convert &to &amp; Convert <to &lt; Convert >to &gt; Convert "to &quot; Convert 'to &#x27; Convert /to &#x2F;
HTML Attribute Encoding	Except for alphanumeric characters, escape all characters with the HTML Entity &#xHH; format including spaces. (HH = Hex Value)
URL Encoding	For standard percent encoding see here. URL encoding should only be used to encode parameter values, not the entire URL or path fragments of a URL.
JavaScript Encoding	Except for alphanumeric characters, escape all characters with the \uXXXX unicode escaping format (XX = Integer)
CSS Hex Encoding	CSS escaping supports \XX and \XXXXXX. Using a two-character escape can cause problems if the next character continues the escape sequence. There are two solutions: - Add a space after the CSS escape (it will be ignored by the CSS parser) - Use the full amount of CSS escaping possible by zero padding the value.

Defense in Depth

Content Security Policy (CSP)

The Content Security Policy (CSP) is a browser mechanism that enables the creation of source allow lists for client-side resources of web applications, e.g., JavaScript, CSS, images, etc. CSP via a special HTTP header instructs the browser to only execute or render resources from those sources.

For example:

Content-Security-Policy: default-src: 'self'; script-src: 'self' static.domain.tld

The above CSP will instruct the web browser to load all resources only from the page's origin and JavaScript source code files from static.domain.tld. For more details on Content Security Policy, including what it does and how to use it, see this article.

X-XSS-Protection Header

This HTTP response header enables the Cross-Site Scripting (XSS) filter built into some modern web browsers. The header is usually enabled by default anyway, so its role is to re-enable the filter for a particular website if it was disabled by the user.

Content Types

To prevent non-HTML HTTP responses from embedding data which might be dangerously interpreted as HTML or JavaScript, it is recommended to always send the Content-Type header in the HTTP response to ensure that browsers interpret it in the way it's intended.

Modern Frameworks

Modern JavaScript frameworks (e.g., AngularJS, ReactJS) or server-side templating systems (e.g., Go Templates) have robust built-in protections against Reflected Cross-Site Scripting.

Testing

Verify that context-aware, preferably automated - or at worst, manual - output escaping protects against reflected, stored, and DOM-based XSS.

• OWASP ASVS: 5.3.1, 5.3.3
• OWASP Testing Guide: Testing for Reflected Cross Site Scripting, Testing for Stored Cross Site Scripting, Testing for DOM-Based Cross Site Scripting

View this in the SecureFlag Knowledge Base

[secure-code-warrior-for-github]

Micro-Learning Topic: Cross-site scripting (Detected by phrase)

Matched on "XSS"

What is this? (2min video)

Reflected cross-site scripting vulnerabilities occur when unescaped input is displayed in the resulting page displayed to the user. When HTML or script is included in the input, it will be processed by a user's browser as HTML or script and can alter the appearance of the page or execute malicious scripts in their user context.

Try this challenge in Secure Code Warrior

[secure-code-warrior-for-github]

Micro-Learning Topic: Stored cross-site scripting (Detected by phrase)

Matched on "Stored XSS"

What is this? (2min video)

Stored cross-site scripting vulnerabilities happen when unescaped input is displayed by the application after successful storage in persistence layers (e.g. database or cache). When HTML or script is included in the input that is stored in the database, and is then rendered into a page without escaping or encoding, it will be processed by a user's browser as HTML or script and can alter the appearance of the page or execute malicious scripts in their user context.

Try this challenge in Secure Code Warrior

Micro-Learning Topic: Reflected cross-site scripting (Detected by phrase)

Matched on "Reflected XSS"

What is this? (2min video)

Reflected cross-site scripting vulnerabilities occur when unescaped input is displayed in the resulting page displayed to the user. When HTML or script is included in the input, it will be processed by a user's browser as HTML or script and can alter the appearance of the page or execute malicious scripts in their user context.

Try this challenge in Secure Code Warrior

Micro-Learning Topic: DOM-based cross-site scripting (Detected by phrase)

Matched on "Dom-based XSS"

What is this? (2min video)

DOM-based cross-site scripting vulnerabilities occur when unescaped input is processed by client-side script and insecurely written into the page Document Object Model (DOM). This will result in immediate changes to the page, potentially without any call to the server. When HTML or script is included in the input, it will be processed by a user's browser as HTML or script and can alter the appearance of the page or execute malicious scripts in their user context.

Try this challenge in Secure Code Warrior