Vulnerabilities	9 via 69 paths
Dependencies	1039
Source	GitHub
Commit	da8c708f

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications

Severity

Critical
High
6
Medium
3
Low

Status

Open
9
Patched
0
Ignored
0

high severity

Asymmetric Resource Consumption (Amplification)

Vulnerable module: body-parser
Introduced through: expo@45.0.8

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › body-parser@1.19.0

Remediation: Upgrade to expo@46.0.0.

Overview

Affected versions of this package are vulnerable to Asymmetric Resource Consumption (Amplification) via the extendedparser and urlencoded functions when the URL encoding process is enabled. An attacker can flood the server with a large number of specially crafted requests.

Remediation

Upgrade body-parser to version 1.20.3 or higher.

References

GitHub Commit

Asymmetric Resource Consumption (Amplification) vulnerability report

high severity

Excessive Platform Resource Consumption within a Loop

Vulnerable module: braces
Introduced through: react-native@0.68.2

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › micromatch@3.1.10 › braces@2.3.2

Remediation: Upgrade to react-native@0.70.0.

Overview

braces is a Bash-like brace expansion, implemented in JavaScript.

Affected versions of this package are vulnerable to Excessive Platform Resource Consumption within a Loop due improper limitation of the number of characters it can handle, through the parse function. An attacker can cause the application to allocate excessive memory and potentially crash by sending imbalanced braces as input.

PoC

const { braces } = require('micromatch');

console.log("Executing payloads...");

const maxRepeats = 10;

for (let repeats = 1; repeats <= maxRepeats; repeats += 1) {
  const payload = '{'.repeat(repeats*90000);

  console.log(`Testing with ${repeats} repeats...`);
  const startTime = Date.now();
  braces(payload);
  const endTime = Date.now();
  const executionTime = endTime - startTime;
  console.log(`Regex executed in ${executionTime / 1000}s.\n`);
}

Remediation

Upgrade braces to version 3.0.3 or higher.

References

Excessive Platform Resource Consumption within a Loop vulnerability report

high severity

Inefficient Regular Expression Complexity

Vulnerable module: micromatch
Introduced through: react-native@0.68.2

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › micromatch@3.1.10

Remediation: Upgrade to react-native@0.70.0.

Overview

Affected versions of this package are vulnerable to Inefficient Regular Expression Complexity due to the use of unsafe pattern configurations that allow greedy matching through the micromatch.braces() function. An attacker can cause the application to hang or slow down by passing a malicious payload that triggers extensive backtracking in regular expression processing.

Remediation

Upgrade micromatch to version 4.0.8 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

high severity

Prototype Poisoning

Vulnerable module: qs
Introduced through: expo@45.0.8

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › body-parser@1.19.0 › qs@6.7.0

Remediation: Upgrade to expo@46.0.0.

Overview

qs is a querystring parser that supports nesting and arrays, with a depth limit.

Affected versions of this package are vulnerable to Prototype Poisoning which allows attackers to cause a Node process to hang, processing an Array object whose prototype has been replaced by one with an excessive length value.

Note: In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000.

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 qs to version 6.2.4, 6.3.3, 6.4.1, 6.5.3, 6.6.1, 6.7.3, 6.8.3, 6.9.7, 6.10.3 or higher.

References

Prototype Poisoning vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

Vulnerable module: semver
Introduced through: expo@45.0.8

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/config@6.0.26 › semver@7.3.2

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › expo-constants@13.1.1 › @expo/config@6.0.26 › semver@7.3.2

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › semver@7.3.2
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › semver@7.3.2

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › semver@7.3.2

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › @expo/config@6.0.26 › semver@7.3.2

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › @expo/image-utils@0.3.21 › semver@7.3.2

Remediation: Upgrade to expo@51.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › semver@7.3.2

Remediation: Upgrade to expo@49.0.0.

…and 5 more

Overview

semver is a semantic version parser used by npm.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

PoC


const semver = require('semver')
const lengths_2 = [2000, 4000, 8000, 16000, 32000, 64000, 128000]

console.log("n[+] Valid range - Test payloads")
for (let i = 0; i =1.2.3' + ' '.repeat(lengths_2[i]) + '<1.3.0';
const start = Date.now()
semver.validRange(value)
// semver.minVersion(value)
// semver.maxSatisfying(["1.2.3"], value)
// semver.minSatisfying(["1.2.3"], value)
// new semver.Range(value, {})

const end = Date.now();
console.log('length=%d, time=%d ms', value.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 semver to version 5.7.2, 6.3.1, 7.5.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Prototype Pollution

Vulnerable module: unset-value
Introduced through: react-native@0.68.2

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › 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: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › 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: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › 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: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › 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

…and 2 more

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
Web browser

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 of Object.

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

Prototype Pollution vulnerability report

medium severity

Server-Side Request Forgery (SSRF)

Vulnerable module: ip
Introduced through: react-native@0.68.2

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-hermes@6.3.1 › ip@1.1.9

Overview

ip is a Node library.

Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF) via the isPublic function, which identifies some private IP addresses as public addresses due to improper parsing of the input. An attacker can manipulate a system that uses isLoopback(), isPrivate() and isPublic functions to guard outgoing network requests to treat certain IP addresses as globally routable by supplying specially crafted IP addresses.

Note

This vulnerability derived from an incomplete fix for CVE-2023-42282

Remediation

There is no fixed version for ip.

References

Server-Side Request Forgery (SSRF) vulnerability report

medium severity

Missing Release of Resource after Effective Lifetime

Vulnerable module: inflight
Introduced through: expo-location@14.2.2, react-native@0.68.2 and others

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo-location@14.2.2 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli-platform-android@7.0.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli-platform-ios@7.0.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › expo-file-system@14.0.0 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/config@6.0.26 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › expo-constants@13.1.1 › @expo/config@6.0.26 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › cacache@15.3.0 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › babel-preset-expo@9.1.0 › babel-plugin-module-resolver@4.1.0 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › expo-constants@13.1.1 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › @expo/config@6.0.26 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/package-manager@0.0.60 › rimraf@3.0.2 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › cacache@15.3.0 › rimraf@3.0.2 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-hermes@6.3.1 › @react-native-community/cli-platform-android@6.3.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › cacache@15.3.0 › @npmcli/move-file@1.1.2 › rimraf@3.0.2 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › tempy@0.7.1 › del@6.1.1 › rimraf@3.0.2 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › react-native-codegen@0.0.17 › jscodeshift@0.13.1 › temp@0.8.4 › rimraf@2.6.3 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › glob@7.1.6 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › @expo/bunyan@4.0.0 › mv@2.1.1 › rimraf@2.4.5 › glob@6.0.4 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro-config@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro-config@0.67.0 › metro@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-transform-worker@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro-config@0.67.0 › metro@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-config@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-config@0.67.0 › metro@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-transform-worker@0.67.0 › metro@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro-config@0.67.0 › metro@0.67.0 › metro-transform-worker@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-config@0.67.0 › metro@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-transform-worker@0.67.0 › metro@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro-config@0.67.0 › metro@0.67.0 › metro-config@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-config@0.67.0 › metro@0.67.0 › metro-transform-worker@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › react-native@0.68.2 › @react-native-community/cli@7.0.4 › @react-native-community/cli-plugin-metro@7.0.4 › metro@0.67.0 › metro-transform-worker@0.67.0 › metro@0.67.0 › metro-config@0.67.0 › metro-cache@0.67.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6

…and 38 more

Overview

Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime via the makeres function due to improperly deleting keys from the reqs object after execution of callbacks. This behavior causes the keys to remain in the reqs object, which leads to resource exhaustion.

Exploiting this vulnerability results in crashing the node process or in the application crash.

Note: This library is not maintained, and currently, there is no fix for this issue. To overcome this vulnerability, several dependent packages have eliminated the use of this library.

To trigger the memory leak, an attacker would need to have the ability to execute or influence the asynchronous operations that use the inflight module within the application. This typically requires access to the internal workings of the server or application, which is not commonly exposed to remote users. Therefore, “Attack vector” is marked as “Local”.

PoC

const inflight = require('inflight');

function testInflight() {
  let i = 0;
  function scheduleNext() {
    let key = `key-${i++}`;
    const callback = () => {
    };
    for (let j = 0; j < 1000000; j++) {
      inflight(key, callback);
    }

    setImmediate(scheduleNext);
  }


  if (i % 100 === 0) {
    console.log(process.memoryUsage());
  }

  scheduleNext();
}

testInflight();

Remediation

There is no fixed version for inflight.

References

Missing Release of Resource after Effective Lifetime vulnerability report

medium severity

Prototype Pollution

Vulnerable module: xml2js
Introduced through: expo-location@14.2.2 and expo@45.0.8

Detailed paths

Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo-location@14.2.2 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo-location@15.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › expo-file-system@14.0.0 › @expo/config-plugins@4.1.5 › xml2js@0.4.23
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › expo-constants@13.1.1 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/prebuild-config@4.0.4 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.
Introduced through: sosmoto@marakoss/sos-moto-app#da8c708f13a858fd5c31130527588db12f2ec555 › expo@45.0.8 › @expo/cli@0.1.7 › @expo/dev-server@0.1.116 › @expo/metro-config@0.3.19 › @expo/config@6.0.26 › @expo/config-plugins@4.1.5 › xml2js@0.4.23

Remediation: Upgrade to expo@49.0.0.

…and 7 more

Overview

Affected versions of this package are vulnerable to Prototype Pollution due to allowing an external attacker to edit or add new properties to an object. This is possible because the application does not properly validate incoming JSON keys, thus allowing the __proto__ property to be edited.

PoC

var parseString = require('xml2js').parseString;

let normal_user_request    = "<role>admin</role>";
let malicious_user_request = "<__proto__><role>admin</role></__proto__>";

const update_user = (userProp) => {
    // A user cannot alter his role. This way we prevent privilege escalations.
    parseString(userProp, function (err, user) {
        if(user.hasOwnProperty("role") && user?.role.toLowerCase() === "admin") {
            console.log("Unauthorized Action");
        } else {
            console.log(user?.role[0]);
        }
    });
}

update_user(normal_user_request);
update_user(malicious_user_request);

Details

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]

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

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
Web browser

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 of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade xml2js to version 0.5.0 or higher.

References

Prototype Pollution vulnerability report

marakoss/sos-moto-app

Vulnerabilities

Dependencies

Source

Commit

Find, fix and prevent vulnerabilities in your code.

high severity

Asymmetric Resource Consumption (Amplification)

Detailed paths

Overview

Remediation

References

high severity

Excessive Platform Resource Consumption within a Loop

Detailed paths

Overview

PoC

Remediation

References

high severity

Inefficient Regular Expression Complexity

Detailed paths

Overview

Remediation

References

high severity

Prototype Poisoning

Detailed paths

Overview

Details

Remediation

References

high severity

Regular Expression Denial of Service (ReDoS)

Detailed paths

Overview

PoC

Details

Remediation

References

high severity

Prototype Pollution

Detailed paths

Overview

Details

Unsafe Object recursive merge

Property definition by path

Types of attacks

Affected environments

How to prevent

For more information on this vulnerability type:

Remediation

References

medium severity

Server-Side Request Forgery (SSRF)

Detailed paths

Overview

Remediation

References

medium severity

Missing Release of Resource after Effective Lifetime

Detailed paths

Overview

PoC

Remediation

References

medium severity

Prototype Pollution

Detailed paths

Overview

PoC

Details

Unsafe Object recursive merge

Property definition by path

Types of attacks

Affected environments

How to prevent

For more information on this vulnerability type:

Remediation

References