Skip to main content

Test Results

jloosli/node-firestore-import-export

Vulnerabilities

 14 via 40 paths

Dependencies

 287

Source

 GitHub

Commit

 58db1841

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 4
  • 10
Status
  • 14
  • 0
  • 0

high severity

Denial of Service (DoS)

  • Vulnerable module: dicer
  • Introduced through: firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › dicer@0.3.1

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS). A malicious attacker can send a modified form to server, and crash the nodejs service. An attacker could sent the payload again and again so that the service continuously crashes.

PoC

await fetch('http://127.0.0.1:8000', { method: 'POST', headers: { ['content-type']: 'multipart/form-data; boundary=----WebKitFormBoundaryoo6vortfDzBsDiro', ['content-length']: '145', connection: 'keep-alive', }, body: '------WebKitFormBoundaryoo6vortfDzBsDiro\r\n Content-Disposition: form-data; name="bildbeschreibung"\r\n\r\n\r\n------WebKitFormBoundaryoo6vortfDzBsDiro--' });

Remediation

There is no fixed version for dicer.

References

Denial of Service (DoS) vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: json-bigint
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gcp-metadata@3.5.0 › json-bigint@0.3.1
    Remediation: Upgrade to @google-cloud/firestore@4.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gcp-metadata@3.5.0 › json-bigint@0.3.1
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › @google-cloud/common@2.4.0 › google-auth-library@5.10.1 › gcp-metadata@3.5.0 › json-bigint@0.3.1
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › gcs-resumable-upload@2.3.3 › google-auth-library@5.10.1 › gcp-metadata@3.5.0 › json-bigint@0.3.1
    Remediation: Upgrade to firebase-admin@9.0.0.

…and 1 more

Overview

json-bigint is a JSON.parse with bigints support

Affected versions of this package are vulnerable to Prototype Pollution via the parse function.

POC

const JSONbig = require('json-bigint')
const json = '{"__proto__":1000000000000000,"c":{"__proto__":[],"length":1e200}}'
const r = JSONbig.parse(json)
console.log(r.toString())

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

  1. Freeze the prototype— use Object.freeze (Object.prototype).

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

  4. Consider using objects without prototypes (for example, Object.create(null)), breaking the prototype chain and preventing pollution.

  5. 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 json-bigint to version 1.0.0 or higher.

References

Prototype Pollution vulnerability report

high severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: node-forge
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to @google-cloud/firestore@4.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › @google-cloud/common@2.4.0 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › gcs-resumable-upload@2.3.3 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › node-forge@0.7.6
    Remediation: Upgrade to firebase-admin@10.0.2.

…and 2 more

Overview

node-forge is a JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to RSA's PKCS#1 v1.5 signature verification code which does not check for tailing garbage bytes after decoding a DigestInfo ASN.1 structure. This can allow padding bytes to be removed and garbage data added to forge a signature when a low public exponent is being used.

Remediation

Upgrade node-forge to version 1.3.0 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: node-forge
  • Introduced through: firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › node-forge@0.7.6
    Remediation: Upgrade to firebase-admin@9.2.0.

Overview

node-forge is a JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.

Affected versions of this package are vulnerable to Prototype Pollution via the util.setPath function.

Note: version 0.10.0 is a breaking change removing the vulnerable functions.

POC:

const nodeforge = require('node-forge');
var obj = {};
nodeforge.util.setPath(obj, ['__proto__', 'polluted'], true);
console.log(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

  • Web browser

How to prevent

  1. Freeze the prototype— use Object.freeze (Object.prototype).

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

  4. Consider using objects without prototypes (for example, Object.create(null)), breaking the prototype chain and preventing pollution.

  5. 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 node-forge to version 0.10.0 or higher.

References

Prototype Pollution vulnerability report

medium severity

Uncontrolled Resource Consumption

  • Vulnerable module: @grpc/grpc-js
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › @grpc/grpc-js@1.3.8
    Remediation: Upgrade to @google-cloud/firestore@6.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › @grpc/grpc-js@1.3.8
    Remediation: Upgrade to firebase-admin@11.1.0.

Overview

@grpc/grpc-js is a gRPC Library for Node

Affected versions of this package are vulnerable to Uncontrolled Resource Consumption via the grpc.max_receive_message_length channel option. An attacker can cause a denial of service by sending messages that exceed the configured limits, which are then buffered or decompressed into memory.

Remediation

Upgrade @grpc/grpc-js to version 1.8.22, 1.9.15, 1.10.9 or higher.

References

Uncontrolled Resource Consumption vulnerability report

medium severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: jsonwebtoken
  • Introduced through: firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › jsonwebtoken@8.5.1
    Remediation: Upgrade to firebase-admin@11.4.1.

Overview

jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)

Affected versions of this package are vulnerable to Use of a Broken or Risky Cryptographic Algorithm such that the library can be misconfigured to use legacy, insecure key types for signature verification. For example, DSA keys could be used with the RS256 algorithm.

Exploitability

Users are affected when using an algorithm and a key type other than the combinations mentioned below:

EC: ES256, ES384, ES512

RSA: RS256, RS384, RS512, PS256, PS384, PS512

RSA-PSS: PS256, PS384, PS512

And for Elliptic Curve algorithms:

ES256: prime256v1

ES384: secp384r1

ES512: secp521r1

Workaround

Users who are unable to upgrade to the fixed version can use the allowInvalidAsymmetricKeyTypes option to true in the sign() and verify() functions to continue usage of invalid key type/algorithm combination in 9.0.0 for legacy compatibility.

Remediation

Upgrade jsonwebtoken to version 9.0.0 or higher.

References

Use of a Broken or Risky Cryptographic Algorithm vulnerability report

medium severity

Improper Restriction of Security Token Assignment

  • Vulnerable module: jsonwebtoken
  • Introduced through: firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › jsonwebtoken@8.5.1
    Remediation: Upgrade to firebase-admin@11.4.1.

Overview

jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)

Affected versions of this package are vulnerable to Improper Restriction of Security Token Assignment via the secretOrPublicKey argument due to misconfigurations of the key retrieval function jwt.verify(). Exploiting this vulnerability might result in incorrect verification of forged tokens when tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm.

Note: This vulnerability affects your application if it supports the usage of both symmetric and asymmetric keys in jwt.verify() implementation with the same key retrieval function.

Remediation

Upgrade jsonwebtoken to version 9.0.0 or higher.

References

Improper Restriction of Security Token Assignment vulnerability report

medium severity

Improper Authentication

  • Vulnerable module: jsonwebtoken
  • Introduced through: firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › jsonwebtoken@8.5.1
    Remediation: Upgrade to firebase-admin@11.4.1.

Overview

jsonwebtoken is a JSON Web Token implementation (symmetric and asymmetric)

Affected versions of this package are vulnerable to Improper Authentication such that the lack of algorithm definition in the jwt.verify() function can lead to signature validation bypass due to defaulting to the none algorithm for signature verification.

Exploitability

Users are affected only if all of the following conditions are true for the jwt.verify() function:

  1. A token with no signature is received.

  2. No algorithms are specified.

  3. A falsy (e.g., null, false, undefined) secret or key is passed.

Remediation

Upgrade jsonwebtoken to version 9.0.0 or higher.

References

Improper Authentication vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: node-forge
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to @google-cloud/firestore@4.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › @google-cloud/common@2.4.0 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › gcs-resumable-upload@2.3.3 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › node-forge@0.7.6
    Remediation: Upgrade to firebase-admin@10.0.2.

…and 2 more

Overview

node-forge is a JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.

Affected versions of this package are vulnerable to Prototype Pollution via the forge.debug API if called with untrusted input.

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

  1. Freeze the prototype— use Object.freeze (Object.prototype).

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

  4. Consider using objects without prototypes (for example, Object.create(null)), breaking the prototype chain and preventing pollution.

  5. 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 node-forge to version 1.0.0 or higher.

References

Prototype Pollution vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: @firebase/util
  • Introduced through: firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @firebase/database@0.6.13 › @firebase/util@0.3.2
    Remediation: Upgrade to firebase-admin@9.4.2.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @firebase/database@0.6.13 › @firebase/component@0.1.19 › @firebase/util@0.3.2
    Remediation: Upgrade to firebase-admin@9.4.2.

Overview

@firebase/util is a wrapper of some Webchannel Features for the Firebase JS SDK.

Affected versions of this package are vulnerable to Prototype Pollution. This vulnerability relates to the deepExtend function within the DeepCopy.ts file. Depending on if user input is provided, an attacker can overwrite and pollute the object prototype of a program.

PoC

const util = require('@firebase/util');
var payload = JSON.parse('{"__proto__": {"polluted": "vulnerable"}}');

const a = {
    nest: {
      number: 1,
      string: '1',
      object: { key: '1' },
      date: new Date(1),
      nest: {
        a: 1
      }
    },
  };

var result = util.deepExtend(a,payload);
console.log({}.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

  • Web browser

How to prevent

  1. Freeze the prototype— use Object.freeze (Object.prototype).

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

  4. Consider using objects without prototypes (for example, Object.create(null)), breaking the prototype chain and preventing pollution.

  5. 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 @firebase/util to version 0.3.4 or higher.

References

Prototype Pollution vulnerability report

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: node-forge
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to @google-cloud/firestore@4.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › @google-cloud/common@2.4.0 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › gcs-resumable-upload@2.3.3 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › node-forge@0.7.6
    Remediation: Upgrade to firebase-admin@10.0.2.

…and 2 more

Overview

node-forge is a JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to RSA's PKCS#1 v1.5 signature verification code which does not properly check DigestInfo for a proper ASN.1 structure. This can lead to successful verification with signatures that contain invalid structures but a valid digest.

Remediation

Upgrade node-forge to version 1.3.0 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: node-forge
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to @google-cloud/firestore@4.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › @google-cloud/common@2.4.0 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › gcs-resumable-upload@2.3.3 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › node-forge@0.7.6
    Remediation: Upgrade to firebase-admin@10.0.2.

…and 2 more

Overview

node-forge is a JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to RSAs PKCS#1` v1.5 signature verification code which is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used.

Remediation

Upgrade node-forge to version 1.3.0 or higher.

References

Improper Verification of Cryptographic Signature vulnerability report

medium severity

Open Redirect

  • Vulnerable module: node-forge
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to @google-cloud/firestore@4.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6 › google-gax@1.15.4 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › @google-cloud/common@2.4.0 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/storage@4.7.2 › gcs-resumable-upload@2.3.3 › google-auth-library@5.10.1 › gtoken@4.1.4 › google-p12-pem@2.0.5 › node-forge@0.10.0
    Remediation: Upgrade to firebase-admin@9.0.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › node-forge@0.7.6
    Remediation: Upgrade to firebase-admin@10.0.2.

…and 2 more

Overview

node-forge is a JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.

Affected versions of this package are vulnerable to Open Redirect via parseUrl function when it mishandles certain uses of backslash such as https:/\/\/\ and interprets the URI as a relative path.

PoC:


// poc.js
var forge = require("node-forge");
var url = forge.util.parseUrl("https:/\/\/\www.github.com/foo/bar");
console.log(url);

// Output of node poc.js:

{
  full: 'https://',
  scheme: 'https',
  host: '',
  port: 443,
  path: '/www.github.com/foo/bar',                        <<<---- path  should be "/foo/bar"
  fullHost: ''
}

Remediation

Upgrade node-forge to version 1.0.0 or higher.

References

Open Redirect vulnerability report

medium severity

Insecure Storage of Sensitive Information

  • Vulnerable module: @google-cloud/firestore
  • Introduced through: @google-cloud/firestore@3.8.6 and firebase-admin@8.13.0

Detailed paths

  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › @google-cloud/firestore@3.8.6
    Remediation: Upgrade to @google-cloud/firestore@6.2.0.
  • Introduced through: node-firestore-import-export@jloosli/node-firestore-import-export#58db1841731d99ea95255e3f05be28f0a8daa0c7 › firebase-admin@8.13.0 › @google-cloud/firestore@3.8.6
    Remediation: Upgrade to firebase-admin@11.1.0.

Overview

@google-cloud/firestore is a Firestore Client Library for Node.js

Affected versions of this package are vulnerable to Insecure Storage of Sensitive Information. An attacker with logs read access can potentially read sensitive information exposed by developers that log objects through this._settings, which could inadvertently log the firestore key.

Remediation

Upgrade @google-cloud/firestore to version 6.2.0 or higher.

References

Insecure Storage of Sensitive Information vulnerability report