Last tested: 20 Feb, 2018

npm-check vulnerabilities

Check for outdated, incorrect, and unused dependencies.

View on npm

npm-check (latest)

Published 13 Feb, 2018

Known vulnerabilities0
Vulnerable paths0
Dependencies267

No known vulnerabilities in npm-check

Security wise, npm-check seems to be a safe package to use.
Over time, new vulnerabilities may be disclosed on npm-check and other packages. To easily find, fix and prevent such vulnerabilties, protect your repos with Snyk!

Vulnerable versions of npm-check

Fixed in 5.0.1

Prototype Pollution

low severity

Detailed paths

  • Introduced through: npm-check@4.1.4 > lodash@3.10.1
  • Introduced through: npm-check@4.1.4 > inquirer@0.11.4 > lodash@3.10.1

Overview

lodash is a javaScript utility library delivering modularity, performance & extras.

Affected versions of this package are vulnerable to Prototype Pollution. The utilities function allow modification of the Object prototype. If an attacker can control part of the structure passed to this function, they could add or modify an existing property.

PoC by Olivier Arteau (HoLyVieR)

var _= require('lodash');
var malicious_payload = '{"__proto__":{"oops":"It works !"}}';

var a = {};
console.log("Before : " + a.oops);
_.merge({}, JSON.parse(malicious_payload));
console.log("After : " + a.oops);

Remediation

Upgrade lodash to version 4.17.5 or higher.

References

Fixed in 4.1.0

Regular Expression Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: glob@4.0.4 > minimatch@0.3.0
  • Introduced through: npm-check@4.0.4 > depcheck@0.4.7 > minimatch@2.0.10

Overview

minimatch is a minimalistic matching library used for converting glob expressions into JavaScript RegExp objects. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach edge cases that causes them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a specially crafted input and cause the service to excessively consume CPU, resulting in a Denial of Service.

An attacker can provide a long value to the minimatch function, which nearly matches the pattern being matched. This will cause the regular expression matching to take a long time, all the while occupying the event loop and preventing it from processing other requests and making the server unavailable (a Denial of Service attack).

You can read more about Regular Expression Denial of Service (ReDoS) on our blog.

Remediation

Upgrade minimatch to version 3.0.2 or greater.

References

Fixed in 4.0.2

Arbitrary Code Injection

high severity
  • Vulnerable module: growl
  • Introduced through: mocha@2.5.3

Detailed paths

  • Introduced through: npm-check@4.0.1 > mocha@2.5.3 > growl@1.9.2

Overview

growl is a package adding Growl support for Nodejs.

Affected versions of the package are vulnerable to Arbitrary Code Injection due to unsafe use of the eval() function. Node.js provides the eval() function by default, and is used to translate strings into Javascript code. An attacker can craft a malicious payload to inject arbitrary commands.

Remediation

Upgrade growl to version 1.10.0 or higher.

References

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: mongoose@4.0.1 > mquery@1.4.0 > debug@0.7.4
  • Introduced through: npm-check@4.0.1 > mocha@2.5.3 > debug@2.2.0

Overview

debug is a JavaScript debugging utility modelled after Node.js core's debugging technique..

debug uses printf-style formatting. Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks via the the %o formatter (Pretty-print an Object all on a single line). It used a regular expression (/\s*\n\s*/g) in order to strip whitespaces and replace newlines with spaces, in order to join the data into a single line. This can cause a very low impact of about 2 seconds matching time for data 50k characters long.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a specially crafted input and cause the service to excessively consume CPU, resulting in a Denial of Service.

You can read more about Regular Expression Denial of Service (ReDoS) on our blog.

Remediation

Upgrade debug to version 2.6.9, 3.1.0 or higher.

References

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: mongoose@4.0.1 > ms@0.1.0
  • Introduced through: npm-check@4.0.1 > mocha@2.5.3 > debug@2.2.0 > ms@0.7.1

Overview

ms is a tiny millisecond conversion utility.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to an incomplete fix for previously reported vulnerability npm:ms:20151024. The fix limited the length of accepted input string to 10,000 characters, and turned to be insufficient making it possible to block the event loop for 0.3 seconds (on a typical laptop) with a specially crafted string passed to ms() function.

Proof of concept

ms = require('ms');
ms('1'.repeat(9998) + 'Q') // Takes about ~0.3s

Note: Snyk's patch for this vulnerability limits input length to 100 characters. This new limit was deemed to be a breaking change by the author. Based on user feedback, we believe the risk of breakage is very low, while the value to your security is much greater, and therefore opted to still capture this change in a patch for earlier versions as well. Whenever patching security issues, we always suggest to run tests on your code to validate that nothing has been broken.

For more information on Regular Expression Denial of Service (ReDoS) attacks, go to our blog.

Disclosure Timeline

  • Feb 9th, 2017 - Reported the issue to package owner.
  • Feb 11th, 2017 - Issue acknowledged by package owner.
  • April 12th, 2017 - Fix PR opened by Snyk Security Team.
  • May 15th, 2017 - Vulnerability published.
  • May 16th, 2017 - Issue fixed and version 2.0.0 released.
  • May 21th, 2017 - Patches released for versions >=0.7.1, <=1.0.0.

Remediation

Upgrade ms to version 2.0.0 or higher.

References

Fixed in 3.0.0

Regular Expression Denial of Service (DoS)

medium severity

Detailed paths

  • Introduced through: npm@2.0.0 > semver@4.0.3
  • Introduced through: hapi@2.0.0 > semver@2.2.1
  • Introduced through: npm-check@2.0.0 > semver-diff@1.0.0 > semver@3.0.1

Overview

The semver module uses regular expressions when parsing a version string. For a carefully crafted input, the time it takes to process these regular expressions is not linear to the length of the input. Since the semver module did not enforce a limit on the version string length, an attacker could provide a long string that would take up a large amount of resources, potentially taking a server down. This issue therefore enables a potential Denial of Service attack. This is a slightly differnt variant of a typical Regular Expression Denial of Service (ReDoS) vulnerability.

Remediation

Update to a version 4.3.2 or greater. From the issue description [2]: "Package version can no longer be more than 256 characters long. This prevents a situation in which parsing the version number can use exponentially more time and memory to parse, leading to a potential denial of service."

References

Fixed in 0.0.4

Prototype Pollution

low severity

Detailed paths

  • Introduced through: cheerio@0.0.3 > soupselect@0.2.0 > nodeunit@0.11.2 > tap@10.7.3 > coveralls@2.13.3 > request@2.79.0 > hawk@3.1.3 > hoek@2.16.3
  • Introduced through: cheerio@0.0.3 > soupselect@0.2.0 > nodeunit@0.11.2 > tap@10.7.3 > coveralls@2.13.3 > request@2.79.0 > hawk@3.1.3 > boom@2.10.1 > hoek@2.16.3
  • Introduced through: cheerio@0.0.3 > soupselect@0.2.0 > nodeunit@0.11.2 > tap@10.7.3 > coveralls@2.13.3 > request@2.79.0 > hawk@3.1.3 > cryptiles@2.0.5 > boom@2.10.1 > hoek@2.16.3
  • Introduced through: cheerio@0.0.3 > soupselect@0.2.0 > nodeunit@0.11.2 > tap@10.7.3 > coveralls@2.13.3 > request@2.79.0 > hawk@3.1.3 > sntp@1.0.9 > hoek@2.16.3
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > hawk@1.0.0 > hoek@0.9.1
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > hawk@1.0.0 > boom@0.4.2 > hoek@0.9.1
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > hawk@1.0.0 > cryptiles@0.2.2 > boom@0.4.2 > hoek@0.9.1
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > hawk@1.0.0 > sntp@0.2.4 > hoek@0.9.1

Overview

hoek is a Utility methods for the hapi ecosystem.

Affected versions of this package are vulnerable to Prototype Pollution. The utilities function allow modification of the Object prototype. If an attacker can control part of the structure passed to this function, they could add or modify an existing property.

PoC by Olivier Arteau (HoLyVieR)

var Hoek = require('hoek');
var malicious_payload = '{"__proto__":{"oops":"It works !"}}';

var a = {};
console.log("Before : " + a.oops);
Hoek.merge({}, JSON.parse(malicious_payload));
console.log("After : " + a.oops);

Remediation

Upgrade hoek to versions 4.2.1, 5.0.3 or higher.

References

Uninitialized Memory Exposure

medium severity

Detailed paths

  • Introduced through: cheerio@0.0.3 > soupselect@0.2.0 > nodeunit@0.11.2 > tap@10.7.3 > coveralls@2.13.3 > request@2.79.0 > tunnel-agent@0.4.3
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > tunnel-agent@0.3.0

Overview

tunnel-agent is HTTP proxy tunneling agent. Affected versions of the package are vulnerable to Uninitialized Memory Exposure.

A possible memory disclosure vulnerability exists when a value of type number is used to set the proxy.auth option of a request request and results in a possible uninitialized memory exposures in the request body.

This is a result of unobstructed use of the Buffer constructor, whose insecure default constructor increases the odds of memory leakage.

Details

Constructing a Buffer class with integer N creates a Buffer of length N with raw (not "zero-ed") memory.

In the following example, the first call would allocate 100 bytes of memory, while the second example will allocate the memory needed for the string "100":

// uninitialized Buffer of length 100
x = new Buffer(100);
// initialized Buffer with value of '100'
x = new Buffer('100');

tunnel-agent's request construction uses the default Buffer constructor as-is, making it easy to append uninitialized memory to an existing list. If the value of the buffer list is exposed to users, it may expose raw server side memory, potentially holding secrets, private data and code. This is a similar vulnerability to the infamous Heartbleed flaw in OpenSSL.

Proof of concept by ChALkeR

require('request')({
  method: 'GET',
  uri: 'http://www.example.com',
  tunnel: true,
  proxy:{
      protocol: 'http:',
      host:"127.0.0.1",
      port:8080,
      auth:80
  }
});

You can read more about the insecure Buffer behavior on our blog.

Similar vulnerabilities were discovered in request, mongoose, ws and sequelize.

Remediation

Upgrade tunnel-agent to version 0.6.0 or higher.

References

Regular Expression Denial of Service (ReDoS)

high severity

Detailed paths

  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > tough-cookie@0.9.15

Overview

tough-cookie Hawk is an HTTP authentication scheme using a message authentication code (MAC) algorithm to provide partial HTTP request cryptographic verification. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach edge cases that causes them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a specially crafted input and cause the service to excessively consume CPU, resulting in a Denial of Service.

An attacker can provide a cookie, which nearly matches the pattern being matched. This will cause the regular expression matching to take a long time, all the while occupying the event loop and preventing it from processing other requests and making the server unavailable (a Denial of Service attack).

You can read more about Regular Expression Denial of Service (ReDoS) on our blog.

Remediation

Upgrade tough-cookie to at version 2.3.0 or greater.

References

Symlink Arbitrary File Overwrite

high severity

Detailed paths

  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > tar@0.1.20
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > node-gyp@0.13.1 > tar@0.1.20

Overview

The tar module prior to version 2.0.0 does not properly normalize symbolic links pointing to targets outside the extraction root. As a result, packages may hold symbolic links to parent and sibling directories and overwrite those files when the package is extracted.

Remediation

Upgrade to version 2.0.0 or greater. If a direct dependency update is not possible, use snyk wizard to patch this vulnerability.

References

Remote Memory Exposure

medium severity

Detailed paths

  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0

Overview

request is a simplified http request client. A potential remote memory exposure vulnerability exists in request. If a request uses a multipart attachment and the body type option is number with value X, then X bytes of uninitialized memory will be sent in the body of the request.

Note that while the impact of this vulnerability is high (memory exposure), exploiting it is likely difficult, as the attacker needs to somehow control the body type of the request. One potential exploit scenario is when a request is composed based on JSON input, including the body type, allowing a malicious JSON to trigger the memory leak.

Details

Constructing a Buffer class with integer N creates a Buffer of length N with non zero-ed out memory. Example:

var x = new Buffer(100); // uninitialized Buffer of length 100
// vs
var x = new Buffer('100'); // initialized Buffer with value of '100'

Initializing a multipart body in such manner will cause uninitialized memory to be sent in the body of the request.

Proof of concept

var http = require('http')
var request = require('request')

http.createServer(function (req, res) {
  var data = ''
  req.setEncoding('utf8')
  req.on('data', function (chunk) {
    console.log('data')
    data += chunk
  })
  req.on('end', function () {
    // this will print uninitialized memory from the client
    console.log('Client sent:\n', data)
  })
  res.end()
}).listen(8000)

request({
  method: 'POST',
  uri: 'http://localhost:8000',
  multipart: [{ body: 1000 }]
},
function (err, res, body) {
  if (err) return console.error('upload failed:', err)
  console.log('sent')
})

Remediation

Upgrade request to version 2.68.0 or higher.

If a direct dependency update is not possible, use snyk wizard to patch this vulnerability.

References

Regular Expression Denial of Service (DoS)

low severity

Detailed paths

  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > hawk@1.0.0

Overview

hawk Hawk is an HTTP authentication scheme using a message authentication code (MAC) algorithm to provide partial HTTP request cryptographic verification. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach edge cases that causes them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a specially crafted input and cause the service to excessively consume CPU, resulting in a Denial of Service.

An attacker can provide a long url, which nearly matches the pattern being matched. This will cause the regular expression matching to take a long time, all the while occupying the event loop and preventing it from processing other requests and making the server unavailable (a Denial of Service attack).

You can read more about Regular Expression Denial of Service (ReDoS) on our blog.

References

Denial of Service (Event Loop Blocking)

medium severity

Detailed paths

  • Introduced through: cordova@0.0.3 > express@3.0.6 > connect@2.7.2 > qs@0.5.1
  • Introduced through: hapi@0.0.3 > express@2.5.11 > qs@0.4.2
  • Introduced through: angular@0.0.3 > express@2.5.10 > qs@0.4.2
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > qs@0.6.6

Overview

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

When parsing a string representing a deeply nested object, qs will block the event loop for long periods of time. Such a delay may hold up the server's resources, keeping it from processing other requests in the meantime, thus enabling a Denial-of-Service attack.

Remediation

Update qs to version 1.0.0 or higher. In these versions, qs enforces a max object depth (along with other limits), limiting the event loop length and thus preventing such an attack.

References

Regular Expression Denial of Service (ReDoS)

medium severity

Detailed paths

  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > tough-cookie@0.9.15

Overview

tough-cookie is RFC6265 Cookies and Cookie Jar for node.js.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. An attacker may pass a specially crafted cookie, causing the server to hang.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a specially crafted input and cause the service to excessively consume CPU, resulting in a Denial of Service.

You can read more about Regular Expression Denial of Service (ReDoS) on our blog.

Remediation

Upgrade to version 2.3.3 or newer.

References

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: cordova@0.0.3 > express@3.0.6 > send@0.1.0 > mime@1.2.6
  • Introduced through: cordova@0.0.3 > express@3.0.6 > connect@2.7.2 > send@0.1.0 > mime@1.2.6
  • Introduced through: hapi@0.0.3 > express@2.5.11 > mime@1.2.4
  • Introduced through: angular@0.0.3 > express@2.5.10 > mime@1.2.4
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > mime@1.2.11
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > form-data@0.1.4 > mime@1.2.11

Overview

mime is a comprehensive, compact MIME type module.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS). It uses regex the following regex /.*[\.\/\\]/ in its lookup, which can cause a slowdown of 2 seconds for 50k characters.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Many Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size), allowing an attacker to exploit this and can cause the program to enter these extreme situations by using a specially crafted input and cause the service to excessively consume CPU, resulting in a Denial of Service.

You can read more about Regular Expression Denial of Service (ReDoS) on our blog.

Remediation

Upgrade mime to versions 1.4.1, 2.0.3 or higher.

References

Prototype Override Protection Bypass

high severity

Detailed paths

  • Introduced through: cordova@0.0.3 > express@3.0.6 > connect@2.7.2 > qs@0.5.1
  • Introduced through: hapi@0.0.3 > express@2.5.11 > qs@0.4.2
  • Introduced through: angular@0.0.3 > express@2.5.10 > qs@0.4.2
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > qs@0.6.6

Overview

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

By default qs protects against attacks that attempt to overwrite an object's existing prototype properties, such as toString(), hasOwnProperty(),etc.

From qs documentation:

By default parameters that would overwrite properties on the object prototype are ignored, if you wish to keep the data from those fields either use plainObjects as mentioned above, or set allowPrototypes to true which will allow user input to overwrite those properties. WARNING It is generally a bad idea to enable this option as it can cause problems when attempting to use the properties that have been overwritten. Always be careful with this option.

Overwriting these properties can impact application logic, potentially allowing attackers to work around security controls, modify data, make the application unstable and more.

In versions of the package affected by this vulnerability, it is possible to circumvent this protection and overwrite prototype properties and functions by prefixing the name of the parameter with [ or ]. e.g. qs.parse("]=toString") will return {toString = true}, as a result, calling toString() on the object will throw an exception.

Example:

qs.parse('toString=foo', { allowPrototypes: false })
// {}

qs.parse("]=toString", { allowPrototypes: false })
// {toString = true} <== prototype overwritten

For more information, you can check out our blog.

Disclosure Timeline

  • February 13th, 2017 - Reported the issue to package owner.
  • February 13th, 2017 - Issue acknowledged by package owner.
  • February 16th, 2017 - Partial fix released in versions 6.0.3, 6.1.1, 6.2.2, 6.3.1.
  • March 6th, 2017 - Final fix released in versions 6.4.0,6.3.2, 6.2.3, 6.1.2 and 6.0.4

Remediation

Upgrade qs to version 6.4.0 or higher. Note: The fix was backported to the following versions 6.3.2, 6.2.3, 6.1.2, 6.0.4.

References

Timing Attack

medium severity

Detailed paths

  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > http-signature@0.10.1

Overview

http-signature is a reference implementation of Joyent's HTTP Signature scheme. Affected versions of the package are vulnerable to Timing Attacks due to time-variable comparison of signatures. il.

The library implemented a character to character comparison, similar to the built-in string comparison mechanism, ===, and not a time constant string comparison. As a result, the comparison will fail faster when the first characters in the signature are incorrect. An attacker can use this difference to perform a timing attack, essentially allowing them to guess the signature one character at a time.

You can read more about timing attacks in Node.js on the Snyk blog.

Remediation

Upgrade http-signature to version 1.0.0 or higher.

References

Denial of Service (Memory Exhaustion)

high severity

Detailed paths

  • Introduced through: cordova@0.0.3 > express@3.0.6 > connect@2.7.2 > qs@0.5.1
  • Introduced through: hapi@0.0.3 > express@2.5.11 > qs@0.4.2
  • Introduced through: angular@0.0.3 > express@2.5.10 > qs@0.4.2
  • Introduced through: npm-check@0.0.3 > npm@1.5.0-alpha-4 > request@2.30.0 > qs@0.6.6

Overview

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

During parsing, the qs module may create a sparse area (an array where no elements are filled), and grow that array to the necessary size based on the indices used on it. An attacker can specify a high index value in a query string, thus making the server allocate a respectively big array. Truly large values can cause the server to run out of memory and cause it to crash - thus enabling a Denial-of-Service attack.

Remediation

Upgrade qs to version 1.0.0 or greater. In these versions, qs introduced a low limit on the index value, preventing such an attack

References