Vulnerabilities |
16 via 310 paths |
---|---|
Dependencies |
612 |
Source |
npm |
Find, fix and prevent vulnerabilities in your code.
high severity
- Vulnerable module: shell-quote
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › shell-quote@1.6.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › shell-quote@1.6.1Remediation: Upgrade to react-native@0.62.0.
Overview
shell-quote is a package used to quote and parse shell commands.
Affected versions of this package are vulnerable to Remote Code Execution (RCE). An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is {A-z]
instead of the correct {A-Za-z]
. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
Remediation
Upgrade shell-quote
to version 1.7.3 or higher.
References
high severity
- Vulnerable module: ansi-regex
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › yargs@9.0.1 › cliui@3.2.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › yargs@9.0.1 › cliui@3.2.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › cliui@3.2.0 › wrap-ansi@2.1.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › inquirer@3.3.0 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › inquirer@3.3.0 › string-width@2.1.1 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › yargs@9.0.1 › string-width@2.1.1 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › inquirer@3.3.0 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › inquirer@3.3.0 › string-width@2.1.1 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › yargs@9.0.1 › string-width@2.1.1 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › string-width@2.1.1 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › string-width@2.1.1 › strip-ansi@4.0.0 › ansi-regex@3.0.1Remediation: Upgrade to react-native@0.62.0.
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to the sub-patterns [[\\]()#;?]*
and (?:;[-a-zA-Z\\d\\/#&.:=?%@~_]*)*
.
PoC
import ansiRegex from 'ansi-regex';
for(var i = 1; i <= 50000; i++) {
var time = Date.now();
var attack_str = "\u001B["+";".repeat(i*10000);
ansiRegex().test(attack_str)
var time_cost = Date.now() - time;
console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
}
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
A
The 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.D
Finally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD
, ABCCCCD
, ABCBCCCD
and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't 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 |
---|---|---|
ACCCX | 3 | 38 |
ACCCCX | 4 | 71 |
ACCCCCX | 5 | 136 |
ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade ansi-regex
to version 4.1.1, 5.0.1, 6.0.1 or higher.
References
high severity
- Vulnerable module: merge
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
Overview
merge is a library that allows you to merge multiple objects into one, optionally creating a new cloned object. Similar to the jQuery.extend but more flexible. Works in Node.js and the browser.
Affected versions of this package are vulnerable to Prototype Pollution. The 'merge' function already checks for 'proto' keys in an object to prevent prototype pollution, but does not check for 'constructor' or 'prototype' keys.
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_
, constructor
and prototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
- Unsafe
Object
recursive merge - Property definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named _proto_
defined with Object.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object
and the source of Object
as defined by the attacker. Properties are then copied on the Object
prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source)
.
lodash
and Hoek
are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to _proto_.myValue
. myValue
is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
Type | Origin | Short description |
---|---|---|
Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf ). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object . In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr) . In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin , then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true , they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
- Application server
- Web server
How to prevent
- Freeze the prototype— use
Object.freeze (Object.prototype)
. - Require schema validation of JSON input.
- Avoid using unsafe recursive merge functions.
- Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution. - As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade merge
to version 2.1.0 or higher.
References
high severity
- Vulnerable module: react-native
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10Remediation: Upgrade to react-native@0.62.3.
Overview
react-native is a library that brings React's declarative UI framework to iOS and Android. With React Native, you use native UI controls and have full access to the native platform.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via validateBaseUrl
function, which can cause the application to use excessive resources, become unresponsive, or crash. This was introduced in react-native version 0.59.0 and fixed in version 0.64.1.
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
A
The 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.D
Finally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD
, ABCCCCD
, ABCBCCCD
and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't 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 |
---|---|---|
ACCCX | 3 | 38 |
ACCCCX | 4 | 71 |
ACCCCCX | 5 | 136 |
ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade react-native
to version 0.64.1, 0.62.3 or higher.
References
high severity
- Vulnerable module: unset-value
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › anymatch@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
Overview
Affected versions of this package are vulnerable to Prototype Pollution via the unset
function in index.js
, because it allows access to object prototype properties.
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_
, constructor
and prototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
- Unsafe
Object
recursive merge - Property definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named _proto_
defined with Object.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object
and the source of Object
as defined by the attacker. Properties are then copied on the Object
prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source)
.
lodash
and Hoek
are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to _proto_.myValue
. myValue
is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
Type | Origin | Short description |
---|---|---|
Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf ). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object . In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr) . In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin , then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true , they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
- Application server
- Web server
How to prevent
- Freeze the prototype— use
Object.freeze (Object.prototype)
. - Require schema validation of JSON input.
- Avoid using unsafe recursive merge functions.
- Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution. - As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade unset-value
to version 2.0.1 or higher.
References
high severity
- Vulnerable module: merge
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › exec-sh@0.2.2 › merge@1.2.1Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › sane@3.1.0 › watch@0.18.0 › exec-sh@0.2.2 › merge@1.2.1
Overview
merge is a library that allows you to merge multiple objects into one, optionally creating a new cloned object. Similar to the jQuery.extend but more flexible. Works in Node.js and the browser.
Affected versions of this package are vulnerable to Prototype Pollution via _recursiveMerge
.
PoC:
const merge = require('merge');
const payload2 = JSON.parse('{"x": {"__proto__":{"polluted":"yes"}}}');
let obj1 = {x: {y:1}};
console.log("Before : " + obj1.polluted);
merge.recursive(obj1, payload2);
console.log("After : " + obj1.polluted);
console.log("After : " + {}.polluted);
Output:
Before : undefined
After : yes
After : yes
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_
, constructor
and prototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
- Unsafe
Object
recursive merge - Property definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named _proto_
defined with Object.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object
and the source of Object
as defined by the attacker. Properties are then copied on the Object
prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source)
.
lodash
and Hoek
are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to _proto_.myValue
. myValue
is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
Type | Origin | Short description |
---|---|---|
Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf ). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object . In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr) . In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin , then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true , they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
- Application server
- Web server
How to prevent
- Freeze the prototype— use
Object.freeze (Object.prototype)
. - Require schema validation of JSON input.
- Avoid using unsafe recursive merge functions.
- Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution. - As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade merge
to version 2.1.1 or higher.
References
medium severity
- Vulnerable module: node-fetch
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
Overview
node-fetch is a light-weight module that brings window.fetch to node.js
Affected versions of this package are vulnerable to Information Exposure when fetching a remote url with Cookie, if it get a Location
response header, it will follow that url and try to fetch that url with provided cookie. This can lead to forwarding secure headers to 3th party.
Remediation
Upgrade node-fetch
to version 2.6.7, 3.1.1 or higher.
References
medium severity
- Vulnerable module: node-fetch
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › fbjs@1.0.0 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-native@0.64.0.
Overview
node-fetch is 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.
Remediation
Upgrade node-fetch
to version 2.6.1, 3.0.0-beta.9 or higher.
References
medium severity
- Vulnerable module: minimist
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › optimist@0.6.1 › minimist@0.0.10
Overview
minimist is a parse argument options module.
Affected versions of this package are vulnerable to Prototype Pollution. The library could be tricked into adding or modifying properties of Object.prototype
using a constructor
or __proto__
payload.
PoC by Snyk
require('minimist')('--__proto__.injected0 value0'.split(' '));
console.log(({}).injected0 === 'value0'); // true
require('minimist')('--constructor.prototype.injected1 value1'.split(' '));
console.log(({}).injected1 === 'value1'); // true
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_
, constructor
and prototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
- Unsafe
Object
recursive merge - Property definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named _proto_
defined with Object.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object
and the source of Object
as defined by the attacker. Properties are then copied on the Object
prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source)
.
lodash
and Hoek
are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to _proto_.myValue
. myValue
is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
Type | Origin | Short description |
---|---|---|
Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf ). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object . In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr) . In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin , then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true , they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
- Application server
- Web server
How to prevent
- Freeze the prototype— use
Object.freeze (Object.prototype)
. - Require schema validation of JSON input.
- Avoid using unsafe recursive merge functions.
- Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution. - As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade minimist
to version 0.2.1, 1.2.3 or higher.
References
medium severity
- Vulnerable module: simple-plist
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › xcode@2.1.0 › simple-plist@1.3.1
Overview
simple-plist is an A wrapper utility for interacting with plist data.
Affected versions of this package are vulnerable to Prototype Pollution via the .parse()
function. This vulnerability can be exploited when parsing a specially crafted XML.
PoC
var xmlPollution = `
<plist version="1.0">
<dict>
<key>__proto__</key>
<dict>
<key>length</key>
<string>polluted</string>
</dict>
</dict>
</plist>`;
console.log(plist.parse(xmlPollution).length); // polluted
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_
, constructor
and prototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
- Unsafe
Object
recursive merge - Property definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named _proto_
defined with Object.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object
and the source of Object
as defined by the attacker. Properties are then copied on the Object
prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source)
.
lodash
and Hoek
are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to _proto_.myValue
. myValue
is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
Type | Origin | Short description |
---|---|---|
Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf ). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object . In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr) . In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin , then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true , they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
- Application server
- Web server
How to prevent
- Freeze the prototype— use
Object.freeze (Object.prototype)
. - Require schema validation of JSON input.
- Avoid using unsafe recursive merge functions.
- Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution. - As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
There is no fixed version for simple-plist
.
References
medium severity
- Vulnerable module: yargs-parser
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › yargs@9.0.1 › yargs-parser@7.0.0Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › yargs@9.0.1 › yargs-parser@7.0.0Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › yargs-parser@7.0.0Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › yargs-parser@7.0.0Remediation: Upgrade to react-native@0.62.0.
Overview
yargs-parser is a mighty option parser used by yargs.
Affected versions of this package are vulnerable to Prototype Pollution. The library could be tricked into adding or modifying properties of Object.prototype
using a __proto__
payload.
Our research team checked several attack vectors to verify this vulnerability:
- It could be used for privilege escalation.
- The library could be used to parse user input received from different sources:
- terminal emulators
- system calls from other code bases
- CLI RPC servers
PoC by Snyk
const parser = require("yargs-parser");
console.log(parser('--foo.__proto__.bar baz'));
console.log(({}).bar);
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_
, constructor
and prototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
- Unsafe
Object
recursive merge - Property definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named _proto_
defined with Object.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object
and the source of Object
as defined by the attacker. Properties are then copied on the Object
prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source)
.
lodash
and Hoek
are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to _proto_.myValue
. myValue
is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
Type | Origin | Short description |
---|---|---|
Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf ). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object . In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr) . In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin , then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true , they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
- Application server
- Web server
How to prevent
- Freeze the prototype— use
Object.freeze (Object.prototype)
. - Require schema validation of JSON input.
- Avoid using unsafe recursive merge functions.
- Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution. - As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade yargs-parser
to version 5.0.1, 13.1.2, 15.0.1, 18.1.1 or higher.
References
medium severity
- Vulnerable module: glob-parent
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › parse-glob@3.0.4 › glob-base@0.3.0 › glob-parent@2.0.0
Overview
glob-parent is a package that helps extracting the non-magic parent path from a glob string.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). The enclosure
regex used to check for strings ending in enclosure containing path separator.
PoC by Yeting Li
var globParent = require("glob-parent")
function build_attack(n) {
var ret = "{"
for (var i = 0; i < n; i++) {
ret += "/"
}
return ret;
}
globParent(build_attack(5000));
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
A
The 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.D
Finally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD
, ABCCCCD
, ABCBCCCD
and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't 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 |
---|---|---|
ACCCX | 3 | 38 |
ACCCCX | 4 | 71 |
ACCCCCX | 5 | 136 |
ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade glob-parent
to version 5.1.2 or higher.
References
medium severity
- Vulnerable module: ws
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › ws@1.1.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › ws@1.1.5Remediation: Upgrade to react-native@0.62.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › ws@1.1.5Remediation: Upgrade to react-native@0.65.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › ws@1.1.5Remediation: Upgrade to react-native@0.65.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › ws@1.1.5Remediation: Upgrade to react-native@0.65.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › react-devtools-core@3.6.3 › ws@3.3.3Remediation: Upgrade to react-native@0.62.0.
Overview
ws is a simple to use websocket client, server and console for node.js.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). A specially crafted value of the Sec-Websocket-Protocol
header can be used to significantly slow down a ws
server.
##PoC
for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
const value = 'b' + ' '.repeat(length) + 'x';
const start = process.hrtime.bigint();
value.trim().split(/ *, */);
const end = process.hrtime.bigint();
console.log('length = %d, time = %f ns', length, end - start);
}
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
A
The 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.D
Finally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD
, ABCCCCD
, ABCBCCCD
and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't 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 |
---|---|---|
ACCCX | 3 | 38 |
ACCCCX | 4 | 71 |
ACCCCCX | 5 | 136 |
ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade ws
to version 7.4.6, 6.2.2, 5.2.3 or higher.
References
medium severity
- Vulnerable module: mem
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › yargs@9.0.1 › os-locale@2.1.0 › mem@1.1.0Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › yargs@9.0.1 › os-locale@2.1.0 › mem@1.1.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › os-locale@2.1.0 › mem@1.1.0
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › yargs@9.0.1 › os-locale@2.1.0 › mem@1.1.0
Overview
mem is an optimization used to speed up consecutive function calls by caching the result of calls with identical input.
Affected versions of this package are vulnerable to Denial of Service (DoS). Old results were deleted from the cache and could cause a memory leak.
details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.
Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.
One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.
When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.
Two common types of DoS vulnerabilities:
High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.
Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm
ws
package
Remediation
Upgrade mem to version 4.0.0 or higher.
References
low severity
- Vulnerable module: braces
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro@0.51.1 › metro-config@0.51.1 › metro@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › @react-native-community/cli@1.12.0 › metro-config@0.51.1 › metro@0.51.1 › metro-config@0.51.1 › metro-cache@0.51.1 › metro-core@0.51.1 › jest-haste-map@24.0.0-alpha.6 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to react-native@0.60.0.
Overview
braces is a Bash-like brace expansion, implemented in JavaScript.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). It used a regular expression (^\{(,+(?:(\{,+\})*),*|,*(?:(\{,+\})*),+)\}
) in order to detects empty braces. This can cause an impact of about 10 seconds matching time for data 50K characters long.
Disclosure Timeline
- Feb 15th, 2018 - Initial Disclosure to package owner
- Feb 16th, 2018 - Initial Response from package owner
- Feb 18th, 2018 - Fix issued
- Feb 19th, 2018 - Vulnerability published
Details
Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.
The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.
Let’s take the following regular expression as an example:
regex = /A(B|C+)+D/
This regular expression accomplishes the following:
A
The 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.D
Finally, we ensure this section of the string ends with a 'D'
The expression would match inputs such as ABBD
, ABCCCCD
, ABCBCCCD
and ACCCCCD
It most cases, it doesn't take very long for a regex engine to find a match:
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total
$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total
The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.
Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.
Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't 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 |
---|---|---|
ACCCX | 3 | 38 |
ACCCCX | 4 | 71 |
ACCCCCX | 5 | 136 |
ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Upgrade braces
to version 2.3.1 or higher.
References
low severity
- Vulnerable module: minimist
- Introduced through: react-native@0.59.10
Detailed paths
-
Introduced through: @jbknowledge/react-form@0.2.0 › react-native@0.59.10 › optimist@0.6.1 › minimist@0.0.10
Overview
minimist is a parse argument options module.
Affected versions of this package are vulnerable to Prototype Pollution due to a missing handler to Function.prototype
.
Note: this is a bypass to CVE-2020-7598
PoC by Snyk
require('minimist')('--_.constructor.constructor.prototype.foo bar'.split(' '));
console.log((function(){}).foo); // bar
Details
Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as _proto_
, constructor
and prototype
. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype
are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.
There are two main ways in which the pollution of prototypes occurs:
- Unsafe
Object
recursive merge - Property definition by path
Unsafe Object recursive merge
The logic of a vulnerable recursive merge function follows the following high-level model:
merge (target, source)
foreach property of source
if property exists and is an object on both the target and the source
merge(target[property], source[property])
else
target[property] = source[property]
When the source object contains a property named _proto_
defined with Object.defineProperty()
, the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object
and the source of Object
as defined by the attacker. Properties are then copied on the Object
prototype.
Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source)
.
lodash
and Hoek
are examples of libraries susceptible to recursive merge attacks.
Property definition by path
There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)
If the attacker can control the value of “path”, they can set this value to _proto_.myValue
. myValue
is then assigned to the prototype of the class of the object.
Types of attacks
There are a few methods by which Prototype Pollution can be manipulated:
Type | Origin | Short description |
---|---|---|
Denial of service (DoS) | Client | This is the most likely attack. DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf ). The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object . In this case, the code fails and is likely to cause a denial of service. For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail. |
Remote Code Execution | Client | Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation. For example: eval(someobject.someattr) . In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code. |
Property Injection | Client | The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens. For example: if a codebase checks privileges for someuser.isAdmin , then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true , they can then achieve admin privileges. |
Affected environments
The following environments are susceptible to a Prototype Pollution attack:
- Application server
- Web server
How to prevent
- Freeze the prototype— use
Object.freeze (Object.prototype)
. - Require schema validation of JSON input.
- Avoid using unsafe recursive merge functions.
- Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution. - As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade minimist
to version 1.2.6 or higher.