[Snyk] Security upgrade node-sass from 4.9.0 to 9.0.0

[midnightcrisis]

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


Snyk has created this PR to fix 29 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Authentication Bypass SNYK-JS-HAWK-6969142	786
	Prototype Pollution SNYK-JS-LODASH-567746	731
	Prototype Pollution SNYK-JS-LODASH-6139239	696
	Prototype Poisoning SNYK-JS-QS-3153490	696
	Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795	696
	Regular Expression Denial of Service (ReDoS) npm:sshpk:20180409	696
	Prototype Pollution SNYK-JS-LODASH-450202	686
	Prototype Pollution SNYK-JS-LODASH-608086	686
	Prototype Pollution SNYK-JS-LODASH-73638	686
	Prototype Pollution SNYK-JS-LODASHMERGEWITH-174136	686
	Prototype Pollution SNYK-JS-Y18N-1021887	686
	Code Injection SNYK-JS-LODASH-1040724	681
	Uninitialized Memory Exposure npm:stringstream:20180511	646
	Prototype Pollution SNYK-JS-JSONSCHEMA-1920922	644
	Prototype Pollution SNYK-JS-LODASHMERGEWITH-174137	636
	Prototype Pollution npm:hoek:20180212	636
	Prototype Pollution npm:lodash:20180130	636
	Prototype Pollution SNYK-JS-AJV-584908	619
	Prototype Pollution SNYK-JS-MINIMIST-559764	601
	Prototype Pollution SNYK-JS-YARGSPARSER-560381	601
	Regular Expression Denial of Service (ReDoS) SNYK-JS-HOSTEDGITINFO-1088355	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905	586
	Regular Expression Denial of Service (ReDoS) SNYK-JS-HAWK-2808852	584
	Arbitrary File Overwrite SNYK-JS-FSTREAM-174725	579
	Prototype Pollution npm:extend:20180424	579
	Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-73639	541
	Prototype Pollution SNYK-JS-MINIMIST-2429795	506
	Regular Expression Denial of Service (ReDoS) SNYK-JS-MINIMATCH-3050818	479
	Insecure Randomness npm:cryptiles:20180710	479

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Prototype Pollution
🦉 Regular Expression Denial of Service (ReDoS)
🦉 Authentication Bypass
🦉 More lessons are available in Snyk Learn

[secure-code-warrior-for-github]

Micro-Learning Topic: Regular expression denial of service (Detected by phrase)

Matched on "Regular Expression Denial of Service"

What is this? (2min video)

Denial of Service (DoS) attacks caused by Regular Expression which causes the system to hang or cause them to work very slowly when attacker sends a well-crafted input(exponentially related to input size).Denial of service attacks significantly degrade the service quality experienced by legitimate users. These attacks introduce large response delays, excessive losses, and service interruptions, resulting in direct impact on availability.

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Authentication bypass (Detected by phrase)

Matched on "Authentication Bypass"

What is this? (2min video)

Improper authentication happens when mechanisms intended to identify the user are flawed (easily tamperable or insufficient). This would allow an attacker to bypass access controls or to easily impersonate a user.

Try a challenge in Secure Code Warrior

Helpful references

• OWASP Improper Authentication prevention cheat sheet - This article is focused on providing clear, simple, actionable guidance for preventing improper authentication flaws in your applications.

Micro-Learning Topic: Code injection (Detected by phrase)

Matched on "Code Injection"

What is this? (2min video)

Code injection happens when an application insecurely accepts input that is subsequently used in a dynamic code evaluation call. If insufficient validation or sanitisation is performed on the input, specially crafted inputs may be able to alter the syntax of the evaluated code and thus alter execution. In a worst case scenario, an attacker could run arbitrary code in the server context and thus perform almost any action on the application server.

Try a challenge in Secure Code Warrior

Helpful references

• OWASP Command Injection - OWASP community page with comprehensive information about Code Injection, and links to various OWASP resources to help detect or prevent it.
• SEI CERT Oracle Coding Standard for Java - Prevent Code Injection - Carnegie Mellon University Software Engineering Institute guidance on preventing code injection vulnerabilities in Java.

Micro-Learning Topic: Denial of service (Detected by phrase)

Matched on "Denial of Service"

The Denial of Service (DoS) attack is focused on making a resource (site, application, server) unavailable for the purpose it was designed. There are many ways to make a service unavailable for legitimate users by manipulating network packets, programming, logical, or resources handling vulnerabilities, among others. Source: https://www.owasp.org/index.php/Denial_of_Service

Try a challenge in Secure Code Warrior

Micro-Learning Topic: Insecure randomness (Detected by phrase)

Matched on "Insecure Randomness"

What is this? (2min video)

This vulnerability manifests when some security construct depends on a random component and this component is somehow guessable -or just not random-.

Try a challenge in Secure Code Warrior

Helpful references

• Java Cryptography Architecture Reference Guide - The SecureRandom Class - Java documentation on usage of the secure PRNG provided by the Java Cryptography Architecture
• Python Standard Library - Secrets Cryptographic Service - Python Standard Library documentation on usage of the secure PRNG provided by Python cryptographic services
• Android Developer Docs - Kotlin - SecureRandom - Android developer documentation on usage of the secure PRNG provided by the Android API.
• .NET Code Quality Rule CA5394: Do not use insecure randomness - A .NET analyzer rule description page that provides a secure and insecure example, as well as information to suppress or disable the warning.
• OWASP Insecure Randomness - OWASP community page with comprehensive information about insecure randomness, and links to various OWASP resources to help detect or prevent it.
• Android Developer Docs - Java - SecureRandom - Android developer documentation on usage of the secure PRNG provided by the Android API.

Micro-Learning Topic: Prototype pollution (Detected by phrase)

Matched on "Prototype Pollution"

What is this? (2min video)

By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This can be problematic if the software depends on existence or non-existence of certain attributes, or uses pre-defined attributes of object prototype (such as hasOwnProperty, toString or valueOf).

Try a challenge in Secure Code Warrior