Last tested: 19 Feb, 2018

sails vulnerabilities

API-driven framework for building realtime apps, using MVC conventions (based on Express and Socket.io)

View on npm

sails (latest)

Published 07 Feb, 2018

Known vulnerabilities3
Vulnerable paths27
Dependencies239

Prototype Pollution

low severity

Detailed paths

  • Introduced through: sails@1.0.0-46 > merge-defaults@0.2.1 > lodash@2.4.2
  • Introduced through: sails@1.0.0-46 > sails-stringfile@0.3.2 > lodash@2.4.2
  • Introduced through: sails@1.0.0-46 > machinepack-process@2.0.2 > machine@12.1.1 > switchback@2.0.0 > lodash@2.4.2
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > machinepack-process@2.0.2 > machine@12.1.1 > switchback@2.0.0 > lodash@2.4.2
  • Introduced through: sails@1.0.0-46 > machinepack-process@2.0.2 > machinepack-json@2.0.1 > machine@12.1.1 > switchback@2.0.0 > lodash@2.4.2
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > machinepack-process@2.0.2 > machinepack-json@2.0.1 > machine@12.1.1 > switchback@2.0.0 > lodash@2.4.2
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > skipper@0.8.4 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > machinepack-redis@1.3.0 > machine@13.0.0-24 > include-all@1.0.8 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > machinepack-redis@1.3.0 > machine@13.0.0-24 > rttc@9.8.2 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > machinepack-process@2.0.2 > machine@12.1.1 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > machinepack-process@2.0.2 > machine@12.1.1 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > machinepack-process@2.0.2 > machinepack-json@2.0.1 > machine@12.1.1 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > machinepack-process@2.0.2 > machinepack-json@2.0.1 > machine@12.1.1 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > machinepack-redis@1.3.0 > machine@13.0.0-24 > switchback@2.0.2 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > reportback@2.0.1 > switchback@2.0.2 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > sort-route-addresses@0.0.1 > lodash@3.10.1
  • Introduced through: sails@1.0.0-46 > machinepack-process@2.0.2 > machine@12.1.1 > rttc@9.3.4 > lodash@3.8.0
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > machinepack-process@2.0.2 > machine@12.1.1 > rttc@9.3.4 > lodash@3.8.0
  • Introduced through: sails@1.0.0-46 > machinepack-process@2.0.2 > machinepack-json@2.0.1 > machine@12.1.1 > rttc@9.3.4 > lodash@3.8.0
  • Introduced through: sails@1.0.0-46 > sails-generate@1.15.5 > machinepack-process@2.0.2 > machinepack-json@2.0.1 > machine@12.1.1 > rttc@9.3.4 > lodash@3.8.0

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

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: sails@1.0.0-46 > machine@15.0.0-22 > anchor@1.2.0 > validator@4.4.0
  • Introduced through: sails@1.0.0-46 > whelk@6.0.0 > machine@15.0.0-22 > anchor@1.2.0 > validator@4.4.0
  • Introduced through: sails@1.0.0-46 > machine-as-action@10.1.1 > machine@15.0.0-22 > anchor@1.2.0 > validator@4.4.0

Overview

validator is a library of string validators and sanitizers.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks. It used a regular expression (^\s*data:([a-z]+\/[a-z0-9\-\+]+(;[a-z\-]+=[a-z0-9\-]+)?)?(;base64)?,[a-z0-9!\$&',\(\)\*\+,;=\-\._~:@\/\?%\s]*\s*$) in order to validate Data URIs. This can cause an impact of about 10 seconds matching time for data 70K characters long.

Disclosure Timeline

  • Feb 15th, 2018 - Initial Disclosure to package owner
  • Feb 16th, 2018 - Initial Response from package owner
  • Feb 18th, 2018 - Fix issued
  • Feb 18th, 2018 - Vulnerability published

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its original and legitimate users. There are many types of DoS attacks, ranging from trying to clog the network pipes to the system by generating a large volume of traffic from many machines (a Distributed Denial of Service - DDoS - attack) to sending crafted requests that cause a system to crash or take a disproportional amount of time to process.

The Regular expression Denial of Service (ReDoS) is a type of Denial of Service attack. Regular expressions are incredibly powerful, but they aren't very intuitive and can ultimately end up making it easy for attackers to take your site down.

Let’s take the following regular expression as an example:

regex = /A(B|C+)+D/

This regular expression accomplishes the following:

  • A The string must start with the letter 'A'
  • (B|C+)+ The string must then follow the letter A with either the letter 'B' or some number of occurrences of the letter 'C' (the + matches one or more times). The + at the end of this section states that we can look for one or more matches of this section.
  • D Finally, we ensure this section of the string ends with a 'D'

The expression would match inputs such as ABBD, ABCCCCD, ABCBCCCD and ACCCCCD

It most cases, it doesn't take very long for a regex engine to find a match:

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCD")'
0.04s user 0.01s system 95% cpu 0.052 total

$ time node -e '/A(B|C+)+D/.test("ACCCCCCCCCCCCCCCCCCCCCCCCCCCCX")'
1.79s user 0.02s system 99% cpu 1.812 total

The entire process of testing it against a 30 characters long string takes around ~52ms. But when given an invalid string, it takes nearly two seconds to complete the test, over ten times as long as it took to test a valid string. The dramatic difference is due to the way regular expressions get evaluated.

Most Regex engines will work very similarly (with minor differences). The engine will match the first possible way to accept the current character and proceed to the next one. If it then fails to match the next one, it will backtrack and see if there was another way to digest the previous character. If it goes too far down the rabbit hole only to find out the string doesn’t match in the end, and if many characters have multiple valid regex paths, the number of backtracking steps can become very large, resulting in what is known as catastrophic backtracking.

Let's look at how our expression runs into this problem, using a shorter string: "ACCCX". While it seems fairly straightforward, there are still four different ways that the engine could match those three C's:

  1. CCC
  2. CC+C
  3. C+CC
  4. 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 validator to version 9.4.1 or higher.

References

Buffer Overflow

medium severity

Detailed paths

  • Introduced through: sails@1.0.0-46 > machine@15.0.0-22 > anchor@1.2.0 > validator@4.4.0
  • Introduced through: sails@1.0.0-46 > whelk@6.0.0 > machine@15.0.0-22 > anchor@1.2.0 > validator@4.4.0
  • Introduced through: sails@1.0.0-46 > machine-as-action@10.1.1 > machine@15.0.0-22 > anchor@1.2.0 > validator@4.4.0

Overview

validator is a library of string validators and sanitizers.

Affected versions of this package are vulnerable to Buffer Overflow. It used a regular expression (/^(?:[A-Z0-9+\/]{4})*(?:[A-Z0-9+\/]{2}==|[A-Z0-9+\/]{3}=|[A-Z0-9+\/]{4})$/i) in order to validate Base64 strings.

Remediation

Upgrade validator to version 5.0.0 or higher.

References

Vulnerable versions of sails

Fixed in 1.0.0-40

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: sails@1.0.0-39 > compression@1.6.2 > debug@2.2.0
  • Introduced through: sails@1.0.0-39 > connect@3.4.1 > debug@2.2.0
  • Introduced through: sails@1.0.0-39 > connect@3.4.1 > finalhandler@0.4.1 > debug@2.2.0
  • Introduced through: sails@1.0.0-39 > express-session@1.14.2 > debug@2.2.0
  • Introduced through: sails@1.0.0-39 > router@1.1.4 > 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: sails@1.0.0-39 > compression@1.6.2 > debug@2.2.0 > ms@0.7.1
  • Introduced through: sails@1.0.0-39 > connect@3.4.1 > debug@2.2.0 > ms@0.7.1
  • Introduced through: sails@1.0.0-39 > connect@3.4.1 > finalhandler@0.4.1 > debug@2.2.0 > ms@0.7.1
  • Introduced through: sails@1.0.0-39 > express-session@1.14.2 > debug@2.2.0 > ms@0.7.1
  • Introduced through: sails@1.0.0-39 > router@1.1.4 > 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 1.0.0-38

Regular Expression Denial of Service (ReDoS)

high severity

Detailed paths

  • Introduced through: sails@1.0.0-37 > express@4.15.2 > fresh@0.5.0
  • Introduced through: sails@1.0.0-37 > express@4.15.2 > send@0.15.1 > fresh@0.5.0
  • Introduced through: sails@1.0.0-37 > express@4.15.2 > serve-static@1.12.1 > send@0.15.1 > fresh@0.5.0
  • Introduced through: sails@1.0.0-37 > serve-favicon@2.3.0 > fresh@0.3.0
  • Introduced through: sails@1.0.0-37 > serve-static@1.10.2 > send@0.13.1 > fresh@0.3.0

Overview

fresh is HTTP response freshness testing.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. A Regular Expression (/ *, */) was used for parsing HTTP headers and take about 2 seconds matching time 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 fresh to version 0.5.2 or higher.

References

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: sails@1.0.0-37 > express@4.15.2 > send@0.15.1 > mime@1.3.4
  • Introduced through: sails@1.0.0-37 > express@4.15.2 > serve-static@1.12.1 > send@0.15.1 > mime@1.3.4
  • Introduced through: sails@1.0.0-37 > serve-static@1.10.2 > send@0.13.1 > mime@1.3.4

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

Fixed in 1.0.0-30

Prototype Override Protection Bypass

high severity

Detailed paths

  • Introduced through: sails@1.0.0-29 > express@4.15.0 > qs@6.3.1

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

Fixed in 1.0.0-18

Regular Expression Denial of Service (ReDoS)

high severity

Detailed paths

  • Introduced through: sails@1.0.0-17 > method-override@2.3.5

Overview

method-override is a module to override HTTP verbs.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS). It uses regex the following regex / *, */ in order to split HTTP headers. An attacker may send specially crafted input in the X-HTTP-Method-Override header and cause a significant slowdown.

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 method-override to version 2.3.10 or higher.

References

Fixed in 1.0.0-17

Cross-site Scripting (XSS)

medium severity
  • Vulnerable module: ejs
  • Introduced through: ejs@2.5.3

Detailed paths

  • Introduced through: sails@1.0.0-16 > ejs@2.5.3

Overview

ejs is a popular JavaScript templating engine. Affected versions of the package are vulnerable to Cross-site Scripting by letting the attacker under certain conditions control and override the filename option causing it to render the value as is, without escaping it. You can read more about this vulnerability on the Snyk blog.

There's also a Remote Code Execution & Denial of Service vulnerabilities caused by the same behaviour.

Details

ejs provides a few different options for you to render a template, two being very similar: ejs.render() and ejs.renderFile(). The only difference being that render expects a string to be used for the template and renderFile expects a path to a template file.

Both functions can be invoked in two ways. The first is calling them with template, data, and options:

ejs.render(str, data, options);

ejs.renderFile(filename, data, options, callback)

The second way would be by calling only the template and data, while ejs lets the options be passed as part of the data:

ejs.render(str, dataAndOptions);

ejs.renderFile(filename, dataAndOptions, callback)

If used with a variable list supplied by the user (e.g. by reading it from the URI with qs or equivalent), an attacker can control ejs options. This includes the filename option, which will be rendered as is when an error occurs during rendering.

ejs.renderFile('my-template', {filename:'<script>alert(1)</script>'}, callback);

The fix introduced in version 2.5.3 blacklisted root options from options passed via the data object.

Disclosure Timeline

  • November 28th, 2016 - Reported the issue to package owner.
  • November 28th, 2016 - Issue acknowledged by package owner.
  • December 06th, 2016 - Issue fixed and version 2.5.5 released.

Remediation

The vulnerability can be resolved by either using the GitHub integration to generate a pull-request from your dashboard or by running snyk wizard from the command-line interface. Otherwise, Upgrade ejs to version 2.5.5 or higher.

References

Denial of Service (DoS)

medium severity
  • Vulnerable module: ejs
  • Introduced through: ejs@2.5.3

Detailed paths

  • Introduced through: sails@1.0.0-16 > ejs@2.5.3

Overview

ejs is a popular JavaScript templating engine. Affected versions of the package are vulnerable to Denial of Service by letting the attacker under certain conditions control and override the localNames option causing it to crash. You can read more about this vulnerability on the Snyk blog.

There's also a Remote Code Execution & Cross-site Scripting vulnerabilities caused by the same behaviour.

Details

ejs provides a few different options for you to render a template, two being very similar: ejs.render() and ejs.renderFile(). The only difference being that render expects a string to be used for the template and renderFile expects a path to a template file.

Both functions can be invoked in two ways. The first is calling them with template, data, and options:

ejs.render(str, data, options);

ejs.renderFile(filename, data, options, callback)

The second way would be by calling only the template and data, while ejs lets the options be passed as part of the data:

ejs.render(str, dataAndOptions);

ejs.renderFile(filename, dataAndOptions, callback)

If used with a variable list supplied by the user (e.g. by reading it from the URI with qs or equivalent), an attacker can control ejs options. This includes the localNames option, which will cause the renderer to crash.

ejs.renderFile('my-template', {localNames:'try'}, callback);

The fix introduced in version 2.5.3 blacklisted root options from options passed via the data object.

Disclosure Timeline

  • November 28th, 2016 - Reported the issue to package owner.
  • November 28th, 2016 - Issue acknowledged by package owner.
  • December 06th, 2016 - Issue fixed and version 2.5.5 released.

Remediation

The vulnerability can be resolved by either using the GitHub integration to generate a pull-request from your dashboard or by running snyk wizard from the command-line interface. Otherwise, Upgrade ejs to version 2.5.5 or higher.

References

Fixed in 1.0.0-15

Remote Code Execution

high severity
  • Vulnerable module: ejs
  • Introduced through: ejs@2.3.4

Detailed paths

  • Introduced through: sails@1.0.0-14 > ejs@2.3.4

Overview

ejs is a popular JavaScript templating engine. Affected versions of the package are vulnerable to Remote Code Execution by letting the attacker under certain conditions control the source folder from which the engine renders include files. You can read more about this vulnerability on the Snyk blog.

There's also a Cross-site Scripting & Denial of Service vulnerabilities caused by the same behaviour.

Details

ejs provides a few different options for you to render a template, two being very similar: ejs.render() and ejs.renderFile(). The only difference being that render expects a string to be used for the template and renderFile expects a path to a template file.

Both functions can be invoked in two ways. The first is calling them with template, data, and options:

ejs.render(str, data, options);

ejs.renderFile(filename, data, options, callback)

The second way would be by calling only the template and data, while ejs lets the options be passed as part of the data:

ejs.render(str, dataAndOptions);

ejs.renderFile(filename, dataAndOptions, callback)

If used with a variable list supplied by the user (e.g. by reading it from the URI with qs or equivalent), an attacker can control ejs options. This includes the root option, which allows changing the project root for includes with an absolute path.

ejs.renderFile('my-template', {root:'/bad/root/'}, callback);

By passing along the root directive in the line above, any includes would now be pulled from /bad/root instead of the path intended. This allows the attacker to take control of the root directory for included scripts and divert it to a library under his control, thus leading to remote code execution.

The fix introduced in version 2.5.3 blacklisted root options from options passed via the data object.

Disclosure Timeline

  • November 27th, 2016 - Reported the issue to package owner.
  • November 27th, 2016 - Issue acknowledged by package owner.
  • November 28th, 2016 - Issue fixed and version 2.5.3 released.

Remediation

The vulnerability can be resolved by either using the GitHub integration to generate a pull-request from your dashboard or by running snyk wizard from the command-line interface. Otherwise, Upgrade ejs to version 2.5.3 or higher.

References

Fixed in 1.0.0-9

Regular Expression Denial of Service (ReDoS)

medium severity

Detailed paths

  • Introduced through: sails@1.0.0-8 > sails-hook-sockets@0.13.13 > socket.io@1.7.3 > socket.io-client@1.7.3 > engine.io-client@1.8.3 > parsejson@0.0.3

Overview

parsejson is a Method that parses a JSON string and returns a JSON object.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. An attacker may pass a specially crafted JSON data, 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

There is no fix available.

References

Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: sails@1.0.0-8 > sails-hook-sockets@0.13.13 > socket.io@1.7.3 > engine.io@1.8.3 > ws@1.1.2
  • Introduced through: sails@1.0.0-8 > sails-hook-sockets@0.13.13 > socket.io@1.7.3 > socket.io-client@1.7.3 > engine.io-client@1.8.3 > ws@1.1.2

Overview

ws is a simple to use websocket client, server and console for node.js.

Affected versions of the package are vulnerable to Denial of Service (DoS) attacks. A specially crafted value of the Sec-WebSocket-Extensions header that used Object.prototype property names as extension or parameter names could be used to make a ws server crash.

PoC:

const WebSocket = require('ws');
const net = require('net');

const wss = new WebSocket.Server({ port: 3000 }, function () {
  const payload = 'constructor';  // or ',;constructor'

  const request = [
    'GET / HTTP/1.1',
    'Connection: Upgrade',
    'Sec-WebSocket-Key: test',
    'Sec-WebSocket-Version: 8',
    `Sec-WebSocket-Extensions: ${payload}`,
    'Upgrade: websocket',
    '\r\n'
  ].join('\r\n');

  const socket = net.connect(3000, function () {
    socket.resume();
    socket.write(request);
  });
});

Remediation

Upgrade ws to version 1.1.5, 3.3.1 or higher.

References

Regular Expression Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: sails@1.0.0-8 > grunt-sync@0.5.2 > glob@4.5.3 > 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 1.0.0-6

Regular Expression Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: sails@1.0.0-5 > express@3.21.2 > connect@2.30.2 > compression@1.5.2 > accepts@1.2.13 > negotiator@0.5.3
  • Introduced through: sails@1.0.0-5 > express@3.21.2 > connect@2.30.2 > serve-index@1.7.3 > accepts@1.2.13 > negotiator@0.5.3

Overview

negotiator is an HTTP content negotiator for Node.js. Versions prior to 0.6.1 are vulnerable to Regular expression Denial of Service (ReDoS) attack when parsing "Accept-Language" http header.

An attacker can provide a long value in the Accept-Language header, which nearly matches the pattern being matched. This will cause the regular expression matching to take a long time, all the while occupying the thread and preventing it from processing other requests. By repeatedly sending multiple such requests, the attacker can make the server unavailable (a Denial of Service attack).

Details

The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time. [1]

Remediation

Upgrade negotiator to to version 0.6.1 or greater.

References

Uninitialized Memory Exposure

medium severity
  • Vulnerable module: concat-stream
  • Introduced through: anchor@0.10.5

Detailed paths

  • Introduced through: sails@1.0.0-5 > anchor@0.10.5 > geojsonhint@1.2.1 > concat-stream@1.4.10

Overview

concat-stream is writable stream that concatenates strings or binary data and calls a callback with the result. Affected versions of the package are vulnerable to Uninitialized Memory Exposure.

A possible memory disclosure vulnerability exists when a value of type number is provided to the stringConcat() method and results in concatenation of uninitialized memory to the stream collection.

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');

concat-stream's stringConcat function 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.

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

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

Remediation

Upgrade concat-stream to version 1.5.2 or higher.

References

Fixed in 0.12.8

Broken CORS

high severity

Detailed paths

  • Introduced through: sails@0.12.7

Overview

sails is API-driven framework for building realtime apps, using MVC conventions (based on Express and Socket.io).

Sails version 0.12.6 and lower allowed the default CORS settings to be very permissive, letting the attacker to bypass the Same Origin Policy.

Remediation

Upgrade sails to version 0.12.7 or higher.

References

Fixed in 0.12.4

Denial of Service (Memory Exhaustion)

high severity

Detailed paths

  • Introduced through: karma@0.12.3 > connect@2.12.0 > qs@0.6.6
  • Introduced through: superagent@0.12.3 > qs@0.5.2
  • Introduced through: sails@0.12.3 > grunt-contrib-watch@0.5.3 > tiny-lr@0.0.4 > qs@0.5.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

Denial of Service (Event Loop Blocking)

medium severity

Detailed paths

  • Introduced through: karma@0.12.3 > connect@2.12.0 > qs@0.6.6
  • Introduced through: superagent@0.12.3 > qs@0.5.2
  • Introduced through: sails@0.12.3 > grunt-contrib-watch@0.5.3 > tiny-lr@0.0.4 > qs@0.5.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

Fixed in 0.12.0-rc9

Regular Expression Denial of Service (DoS)

medium severity

Detailed paths

  • Introduced through: sails@0.12.0-rc8 > express-handlebars@2.0.1 > handlebars@3.0.3 > uglify-js@2.3.6

Overview

The parse() function in the uglify-js package prior to version 2.6.0 is vulnerable to regular expression denial of service (ReDoS) attacks when long inputs of certain patterns are processed.

Details

"The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time." 1

Remediation

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

References

Content Injection (XSS)

medium severity

Detailed paths

  • Introduced through: sails@0.12.0-rc8 > express-handlebars@2.0.1 > handlebars@3.0.3

Overview

When using attributes without quotes in a handlebars template, an attacker can manipulate the input to introduce additional attributes, potentially executing code. This may lead to a Cross-site Scripting (XSS) vulnerability, assuming an attacker can influence the value entered into the template. If the handlebars template is used to render user-generated content, this vulnerability may escalate to a persistent XSS vulnerability.

Details

Example:

Assume handlebars was used to display user comments and avatar, using the following template: <img src={{avatarUrl}}><pre>{{comment}}</pre>

If an attacker spoofed their avatar URL and provided the following value: http://evil.org/avatar.png onload=alert(document.cookie)

The resulting HTML would be the following, triggering the script once the image loads: <img src=http://evil.org/avatar.png onload=alert(document.cookie)><pre>Gotcha!</pre>

References

Improper minification of non-boolean comparisons

high severity

Detailed paths

  • Introduced through: sails@0.12.0-rc8 > express-handlebars@2.0.1 > handlebars@3.0.3 > uglify-js@2.3.6

Overview

uglify-js is a JavaScript parser, minifier, compressor and beautifier toolkit.

Tom MacWright discovered that UglifyJS versions 2.4.23 and earlier are affected by a vulnerability which allows a specially crafted Javascript file to have altered functionality after minification. This bug was demonstrated by Yan to allow potentially malicious code to be hidden within secure code, activated by minification.

Details

In Boolean algebra, DeMorgan's laws describe the relationships between conjunctions (&&), disjunctions (||) and negations (!). In Javascript form, they state that:

 !(a && b) === (!a) || (!b)
 !(a || b) === (!a) && (!b)

The law does not hold true when one of the values is not a boolean however.

Vulnerable versions of UglifyJS do not account for this restriction, and erroneously apply the laws to a statement if it can be reduced in length by it.

Consider this authentication function:

function isTokenValid(user) {
    var timeLeft =
        !!config && // config object exists
        !!user.token && // user object has a token
        !user.token.invalidated && // token is not explicitly invalidated
        !config.uninitialized && // config is initialized
        !config.ignoreTimestamps && // don't ignore timestamps
        getTimeLeft(user.token.expiry); // > 0 if expiration is in the future

    // The token must not be expired
    return timeLeft > 0;
}

function getTimeLeft(expiry) {
  return expiry - getSystemTime();
}

When minified with a vulnerable version of UglifyJS, it will produce the following insecure output, where a token will never expire:

( Formatted for readability )

function isTokenValid(user) {
    var timeLeft = !(                       // negation
        !config                             // config object does not exist
        || !user.token                      // user object does not have a token
        || user.token.invalidated           // token is explicitly invalidated
        || config.uninitialized             // config isn't initialized
        || config.ignoreTimestamps          // ignore timestamps
        || !getTimeLeft(user.token.expiry)  // > 0 if expiration is in the future
    );
    return timeLeft > 0
}

function getTimeLeft(expiry) {
    return expiry - getSystemTime()
}

Remediation

Upgrade UglifyJS to version 2.4.24 or higher.

References

Fixed in 0.12.0-rc6

Insecure Randomness

medium severity

Detailed paths

  • Introduced through: sails@0.12.0-rc5 > sails-hook-sockets@0.12.3 > socket.io@1.4.8 > engine.io@1.6.11 > ws@1.1.0
  • Introduced through: sails@0.12.0-rc5 > sails-hook-sockets@0.12.3 > socket.io-client@1.4.8 > engine.io-client@1.6.11 > ws@1.0.1
  • Introduced through: sails@0.12.0-rc5 > sails-hook-sockets@0.12.3 > socket.io@1.4.8 > socket.io-client@1.4.8 > engine.io-client@1.6.11 > ws@1.0.1

Overview

ws is a simple to use websocket client, server and console for node.js.

Affected versions of the package use the cryptographically insecure Math.random() which can produce predictable values and should not be used in security-sensitive context.

Details

Computers are deterministic machines, and as such are unable to produce true randomness. Pseudo-Random Number Generators (PRNGs) approximate randomness algorithmically, starting with a seed from which subsequent values are calculated.

There are two types of PRNGs: statistical and cryptographic. Statistical PRNGs provide useful statistical properties, but their output is highly predictable and forms an easy to reproduce numeric stream that is unsuitable for use in cases where security depends on generated values being unpredictable. Cryptographic PRNGs address this problem by generating output that is more difficult to predict. For a value to be cryptographically secure, it must be impossible or highly improbable for an attacker to distinguish between it and a truly random value. In general, if a PRNG algorithm is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts.

You can read more about node's insecure Math.random() in Mike Malone's post.

Remediation

Upgrade ws to version 1.1.2 or higher.

References

Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: sails@0.12.0-rc5 > sails-hook-sockets@0.12.3 > socket.io@1.4.8 > engine.io@1.6.11 > ws@1.1.0
  • Introduced through: sails@0.12.0-rc5 > sails-hook-sockets@0.12.3 > socket.io-client@1.4.8 > engine.io-client@1.6.11 > ws@1.0.1
  • Introduced through: sails@0.12.0-rc5 > sails-hook-sockets@0.12.3 > socket.io@1.4.8 > socket.io-client@1.4.8 > engine.io-client@1.6.11 > ws@1.0.1

Overview

The ws package does not limit the size of an incoming payload before it is processed by default. As a result, a very large payload (over 256MB in size) can lead to a failed allocation and crash the node process - enabling a Denial of Service attack.

While 256MB may seem excessive, note that the attack is likely to be sent from another server, not an end-user computer, using data-center connection speeds. In those speeds, a payload of this size can be transmitted in seconds.

Remediation

Update to version 1.1.1 or greater, which sets a default maxPayload of 100MB. If you cannot upgrade, apply a Snyk patch, or provide ws with options setting the maxPayload to an appropriate size that is smaller than 256MB.

References

Fixed in 0.12.0-rc5

Prototype Pollution

low severity

Detailed paths

  • Introduced through: sails@0.12.0-rc4 > grunt-contrib-less@1.0.0 > less@2.7.3 > request@2.81.0 > hawk@3.1.3 > hoek@2.16.3
  • Introduced through: sails@0.12.0-rc4 > grunt-contrib-less@1.0.0 > less@2.7.3 > request@2.81.0 > hawk@3.1.3 > boom@2.10.1 > hoek@2.16.3
  • Introduced through: sails@0.12.0-rc4 > grunt-contrib-less@1.0.0 > less@2.7.3 > request@2.81.0 > hawk@3.1.3 > cryptiles@2.0.5 > boom@2.10.1 > hoek@2.16.3
  • Introduced through: sails@0.12.0-rc4 > grunt-contrib-less@1.0.0 > less@2.7.3 > request@2.81.0 > hawk@3.1.3 > sntp@1.0.9 > hoek@2.16.3

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

Insecure Defaults

high severity

Detailed paths

  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io-client@1.3.7 > engine.io-client@1.5.4
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io@1.3.7 > socket.io-client@1.3.7 > engine.io-client@1.5.4

Overview

engine.io-client, the client for engine.io and socket.io, disables the core SSL/TLS verification checks by default.

This allows an active attacker, for instance one operating a malicious WiFi, to intercept these encrypted connections using the attacker's spoofed certificate and keys. Doing so compromises the data communicated over this channel, as well as allowing an attacker to impersonate both the server and the client during the live session, sending spoofed data to either side.

Remediation

Update to version 1.6.9 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: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io@1.3.7 > engine.io@1.5.4 > ws@0.8.0
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io-client@1.3.7 > engine.io-client@1.5.4 > ws@0.8.0
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io@1.3.7 > socket.io-client@1.3.7 > engine.io-client@1.5.4 > ws@0.8.0

Overview

ws is a simple to use websocket client, server and console for node.js. Affected versions of the package are vulnerable to Uninitialized Memory Exposure.

A client side memory disclosure vulnerability exists in ping functionality of the ws service. When a client sends a ping request and provides an integer value as ping data, it will result in leaking an uninitialized memory buffer.

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');

This would allocate 100 bytes of memory in the first example and just 3 bytes with 100 as value in the second example.

ws's ping function 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 memory, potentially holding secrets, private data and code.

Proof of Concept:

var ws = require('ws')

var server = new ws.Server({ port: 9000 })
var client = new ws('ws://localhost:9000')

client.on('open', function () {
  console.log('open')
  client.ping(50) // this makes the client allocate an uninitialized buffer of 50 bytes and send it to the server

  client.on('pong', function (data) {
    console.log('got pong')
    console.log(data)
  })
})

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

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

References

Regular Expression Denial of Service (DoS)

medium severity

Detailed paths

  • Introduced through: sails@0.12.0-rc4 > connect@2.29.1 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > express@3.20.2 > connect@2.29.1 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > connect@2.29.1 > express-session@1.10.4 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > express@3.20.2 > connect@2.29.1 > express-session@1.10.4 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > connect@2.29.1 > finalhandler@0.3.4 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > express@3.20.2 > connect@2.29.1 > finalhandler@0.3.4 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > express@3.20.2 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > express@3.20.2 > send@0.12.2 > debug@2.1.3 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > express@3.20.2 > send@0.12.2 > ms@0.7.0
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io@1.3.7 > debug@2.1.0 > ms@0.6.2
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io-client@1.3.7 > engine.io-client@1.5.4 > debug@1.0.4 > ms@0.6.2
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io@1.3.7 > socket.io-client@1.3.7 > engine.io-client@1.5.4 > debug@1.0.4 > ms@0.6.2
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io@1.3.7 > engine.io@1.5.4 > debug@1.0.3 > ms@0.6.2
  • Introduced through: sails@0.12.0-rc4 > sails-hook-sockets@0.11.29 > socket.io@1.3.7 > socket.io-adapter@0.3.1 > debug@1.0.2 > ms@0.6.2

Overview

ms is a tiny milisecond conversion utility.

Affected versions of this package are vulnerable to a Regular expression Denial of Service (ReDoS) attack when converting a time period string (i.e. "2 days", "1h") into milliseconds integer. A malicious user could pas extremely long strings to ms(), causing the server take a long time to process, subsequently blocking the event loop for that extended period.

Details

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.

Remediation

Upgrade ms to version 0.7.1.

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

References

Fixed in 0.12.0-rc4

Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: sails@0.12.0-rc3

Overview

sails is API-driven framework for building realtime apps, using MVC conventions (based on Express and Socket.io). Affected versions of the package are vulnerable to a Denial of Service (DoS) attack by sending an OPTIONS request for an undefined route, emitted on the socket.io REST interface. This causes sails to become unresponsive.

Remediation

Upgrade sails to version 0.12.0-rc4 or higher.

References

Fixed in 0.12.0

Remote Memory Exposure

medium severity

Detailed paths

  • Introduced through: sails@0.11.6-1 > grunt-contrib-less@0.11.1 > less@1.7.5 > request@2.40.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

Timing Attack

medium severity

Detailed paths

  • Introduced through: sails@0.11.6-1 > grunt-contrib-less@0.11.1 > less@1.7.5 > request@2.40.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

Regular Expression Denial of Service (DoS)

low severity

Detailed paths

  • Introduced through: sails@0.11.6-1 > grunt-contrib-less@0.11.1 > less@1.7.5 > request@2.40.0 > hawk@1.1.1

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

Uninitialized Memory Exposure

medium severity

Detailed paths

  • Introduced through: sails@0.11.6-1 > grunt-contrib-less@0.11.1 > less@1.7.5 > request@2.40.0 > tunnel-agent@0.4.3

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

Fixed in 0.11.4

Root Path Disclosure

low severity

Detailed paths

  • Introduced through: sails@0.11.3 > connect@2.25.0 > serve-static@1.5.4
  • Introduced through: sails@0.11.3 > express@3.16.0 > connect@2.25.0 > serve-static@1.5.4

Overview:

root path disclosure vulnerability in express.static, res.sendfile, and res.sendFile

Original description taken from the Node Security Project

Recommendations:

  • Update to version 1.8.1 or greater.

References:

Regular Expression Denial of Service (DoS)

medium severity

Detailed paths

  • Introduced through: sinopia@0.11.3 > semver@3.0.1
  • Introduced through: sails@0.11.3 > semver@2.2.1
  • Introduced through: sails@0.11.3 > express-handlebars@1.0.3 > 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

Cross-site Scripting due to improper file and directory names escaping

medium severity

Detailed paths

  • Introduced through: sails@0.11.3 > connect@2.25.0 > serve-index@1.1.6
  • Introduced through: sails@0.11.3 > express@3.16.0 > connect@2.25.0 > serve-index@1.1.6

Overview

When using serve-index middleware version < 1.6.3 file and directory names are not escaped in HTML output. If remote users can influence file or directory names, this can trigger a persistent XSS attack.

Source: Node Security Project

Remediation

Upgrade to version 1.6.3 or greater

References

Root Path Disclosure

medium severity

Detailed paths

  • Introduced through: karma@0.11.3 > connect@2.8.8 > send@0.1.4
  • Introduced through: sails@0.11.3 > express@3.16.0 > send@0.8.1
  • Introduced through: sails@0.11.3 > connect@2.25.0 > serve-static@1.5.4 > send@0.8.5
  • Introduced through: sails@0.11.3 > express@3.16.0 > connect@2.25.0 > serve-static@1.5.4 > send@0.8.5

Overview

Send is a library for streaming files from the file system as an http response. It supports partial responses (Ranges), conditional-GET negotiation, high test coverage, and granular events which may be leveraged to take appropriate actions in your application or framework.

A root path disclosure vulnerability exists in send versions prior to 0.11.1.

Remediation

Upgrade send to version 0.11.1. or greater.

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

References

Directory Traversal

medium severity

Detailed paths

  • Introduced through: karma@0.11.3 > connect@2.8.8 > send@0.1.4
  • Introduced through: sails@0.11.3 > express@3.16.0 > send@0.8.1

Overview

When relying on the root option to restrict file access it may be possible for an application consumer to escape out of the restricted directory and access files in a similarly named directory. For example, static(_dirname + '/public') would allow access to _dirname + '/public-restricted'.

Source: Node Security Project

Remediation

Upgrade to a version greater than or equal to 0.8.4.

References

Open Redirect

low severity

Detailed paths

  • Introduced through: sails@0.11.3 > connect@2.25.0 > serve-static@1.5.4
  • Introduced through: sails@0.11.3 > express@3.16.0 > connect@2.25.0 > serve-static@1.5.4

Overview

When using serve-static middleware version < 1.7.2 and it's configured to mount at the root, it creates an open redirect on the site.

Source: Node Security Project

Details

For example:

If a user visits http://example.com//www.google.com/%2e%2e they will be redirected to //www.google.com/%2e%2e, which some browsers interpret as http://www.google.com/%2e%2e.

Remediation

  • Update to version 1.7.2 or greater (or 1.6.5 if sticking to the 1.6.x line).
  • Disable redirects if not using the feature with 'redirect: false' option and cannot upgrade.

References

Fixed in 0.11.0

Non-Constant Time String Comparison

medium severity

Detailed paths

  • Introduced through: karma@0.10.5 > connect@2.8.8 > cookie-signature@1.0.1
  • Introduced through: sails@0.10.5 > express@3.4.3 > cookie-signature@1.0.1
  • Introduced through: sails@0.10.5 > express@3.4.3 > connect@2.10.1 > cookie-signature@1.0.1

Overview

'cookie-signature' is a library for signing cookies.

Versions before 1.0.4 of the library use 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 token are incorrect. An attacker can use this difference to perform a timing attack, essentially allowing them to guess the secret one character at a time.

You can read more about timing attacks in Node.js on the Snyk blog: https://snyk.io/blog/node-js-timing-attack-ccc-ctf/

Remediation

Upgrade to 1.0.4 or greater.

References

Cross-site Scripting (XSS)

medium severity

Detailed paths

  • Introduced through: sails@0.10.5 > express@3.4.3

Overview

express is a minimalist web framework.

Affected versions of this package do not enforce the user's browser to set a specific charset in the content-type header while displaying 400 level response messages. This could be used by remote attackers to perform a cross-site scripting attack, by using non-standard encodings like UTF-7.

Recommendations

Update express to 3.11.0, 4.5.0 or higher.

References

Fixed in 0.10.0-max

Cross-site Scripting (XSS)

medium severity

Detailed paths

  • Introduced through: sails@0.9.17 > waterline@0.9.16 > anchor@0.9.13 > validator@3.3.0

Overview

validator is a library of string validators and sanitizers.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in IE9 due to unescaped backticks.

Details

Cross-Site Scripting (XSS) attacks occur when an attacker tricks a user’s browser to execute malicious JavaScript code in the context of a victim’s domain. Such scripts can steal the user’s session cookies for the domain, scrape or modify its content, and perform or modify actions on the user’s behalf, actions typically blocked by the browser’s Same Origin Policy.

These attacks are possible by escaping the context of the web application and injecting malicious scripts in an otherwise trusted website. These scripts can introduce additional attributes (say, a "new" option in a dropdown list or a new link to a malicious site) and can potentially execute code on the clients side, unbeknown to the victim. This occurs when characters like \< > \" \' are not escaped properly.

There are a few types of XSS:

  • Persistent XSS is an attack in which the malicious code persists into the web app’s database.
  • Reflected XSS is an which the website echoes back a portion of the request. The attacker needs to trick the user into clicking a malicious link (for instance through a phishing email or malicious JS on another page), which triggers the XSS attack.
  • DOM-based XSS is an that occurs purely in the browser when client-side JavaScript echoes back a portion of the URL onto the page. DOM-Based XSS is notoriously hard to detect, as the server never gets a chance to see the attack taking place.

Remediation

Upgrade validator to version 3.35.0 or higher.

References

Regular Expression Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: sails@0.9.17 > waterline@0.9.16 > anchor@0.9.13 > validator@3.3.0

Overview

validator is a library of string validators and sanitizers.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks. It used a regular expression in order to validate URLs.

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. 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

Update to version 3.22.1 or greater.

References

Insecure Randomness

medium severity

Detailed paths

  • Introduced through: sails@0.9.17 > node-uuid@1.4.0

Overview

A bug in node-uuid prior to 1.4.4 caused it to use the cryptographically insecure Math.random which can produce predictable values and should not be used in security-sensitive context.

Remediation

Upgrade to version 1.4.4 or greater.

References

Fixed in 0.9.5

methodOverride Middleware Reflected Cross-site Scripting (XSS)

medium severity

Detailed paths

  • Introduced through: sails@0.9.4 > express@3.2.6 > connect@2.7.11

Overview

Connect is a stack of middleware that is executed in order in each request.

The "methodOverride" middleware allows the http post to override the method of the request with the value of the _method post key or with the header "x-http-method-override".

Because the user post input was not checked, req.method could contain any kind of value. Because the req.method did not match any common method VERB, connect answered with a 404 page containing the "Cannot [method] [url]" content. The method was not properly encoded for output in the browser.

Source: Node Security Project

Details

Example

~ curl "localhost:3000" -d "_method=<script src=http://nodesecurity.io/xss.js></script>"
Cannot <SCRIPT SRC=HTTP://NODESECURITY.IO/XSS.JS></SCRIPT> /

Mitigation factors

Update to the newest version of Connect or disable methodOverride. It is not possible to avoid the vulnerability if you have enabled this middleware in the top of your stack.

History

Fixed in 0.9.0

Denial of Service (DoS)

medium severity

Detailed paths

  • Introduced through: sails@0.8.895 > connect@1.8.3
  • Introduced through: sails@0.8.895 > express@2.5.11 > connect@1.9.2

Overview

connect is a high performance middleware framework.

Affected versions of the package are vulnerable to Denial of Service (DoS) attacks. It is possible to crash the node server by requesting a url with a trailing backslash in the end.

Remediation

Upgrade connect to version 2.0.0 or higher.

References

Insecure Randomness

high severity

Detailed paths

  • Introduced through: sails@0.8.895 > asset-rack@2.0.6 > browserify@1.17.3 > crypto-browserify@0.4.0

Overview

crypto-browserify is implementation of crypto for the browser.

Affected versions of the package are vulnerable to Insecure Randomness due to using the cryptographically insecure Math.random(). This function can produce predictable values and should not be used in security-sensitive context.

Details

Computers are deterministic machines, and as such are unable to produce true randomness. Pseudo-Random Number Generators (PRNGs) approximate randomness algorithmically, starting with a seed from which subsequent values are calculated.

There are two types of PRNGs: statistical and cryptographic. Statistical PRNGs provide useful statistical properties, but their output is highly predictable and forms an easy to reproduce numeric stream that is unsuitable for use in cases where security depends on generated values being unpredictable. Cryptographic PRNGs address this problem by generating output that is more difficult to predict. For a value to be cryptographically secure, it must be impossible or highly improbable for an attacker to distinguish between it and a truly random value. In general, if a PRNG algorithm is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts.

You can read more about node's insecure Math.random() in Mike Malone's post.

Remediation

Upgrade crypto-browserify to version 2.1.11 or higher.

References

Denial of Service (DoS)

high severity

Detailed paths

  • Introduced through: sails@0.8.895

Overview

sails is API-driven framework for building realtime apps, using MVC conventions (based on Express and Socket.io). Affected versions of the package are vulnerable to a Denial of Service (DoS) attack.

Remediation

Upgrade sails to version 0.9.0 or higher.

References

Insecure Randomness

medium severity

Detailed paths

  • Introduced through: sails@0.8.895 > socket.io@0.9.6

Overview

socket.io is a node.js realtime framework server. Affected versions of the package are vulnerable to Insecure Randomness due to the cryptographically insecure Math.random function which can produce predictable values and should not be used in security-sensitive context.

Remediation

Upgrade socket.io to version 0.9.7 or higher.

References

Potential Script Injection

medium severity

Detailed paths

  • Introduced through: sails@0.8.895 > asset-rack@2.0.6 > browserify@1.17.3 > syntax-error@0.0.1

Overview

There was a security vulnerability where a malicious file could execute code when browserified. Make sure your installation of browserify is using syntax-error@1.1.1 or later.

Source: Node Security Project

Details

The vulnerability involves breaking out of Function(), which was used to check syntax for more informative errors. In node 0.10, Function() seems to be implemented in terms of eval(), so malicious code can execute even if the function returned by Function() was never called. node 0.11 does not appear to be vulnerable.

Thanks to [Cal Leeming] (cal@iops.io) for discovering and disclosing this bug!

Remediation

Update to version 1.1.1 or greater. If this is being used in conjunction with browserify, update browserify to 4.2.1 or greater.

References

Regular Expression Denial of Service (ReDoS)

high severity

Detailed paths

  • Introduced through: sails@0.8.895 > forever@0.10.11 > timespan@2.3.0

Overview

timespan is a JavaScript TimeSpan library for node.js (and soon the browser).

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS). It parses dates using regex strings, which may cause a slowdown of 10 seconds per 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

There is no fix version for timespan.

References

Fixed in 0.7.0

Cross-site Scripting (XSS)

medium severity

Detailed paths

  • Introduced through: sails@0.0.0-2 > sequelize@1.5.0-beta-2 > validator@0.3.9

Overview

The validator module for Node.js contains functionality meant to filter potential XSS attacks (a filter called xss). A method of bypassing the filter via an encoded URL has been publicly disclosed. In general, because the function’s filtering is blacklist-based it is likely that other bypasses will be discovered in the future. Developers are encouraged not to use the xss filter function in this package.

Source: Node Security Project

Details

The xss() function removes the word "javascript" when contained inside an attribute. However, it does not properly handle cases where characters have been hex-encoded. As a result, it is possible to build an input that bypasses the filter but which the browser will accept as valid JavaScript.

For example, browsers interpret abc as abc.

Remediation

Upgrade to the latest version of this library. However, it should be noted that the fix for this vulnerability was to remove the xss filter functionality. Seek another library to provide proper output encoding.

References

Cross-site Scripting (XSS)

medium severity

Detailed paths

  • Introduced through: sails@0.0.0-2 > sequelize@1.5.0-beta-2 > validator@0.3.9

Overview

The validator module for Node.js contains functionality meant to filter potential XSS attacks (a filter called xss). Several ways to bypass the filter were discovered. In general, because the function’s filtering is blacklist-based it is likely that other bypasses will be discovered in the future. Developers are encouraged not to use the xss filter function in this package.

Source: Node Security Project

Details

Various inputs that could bypass the filter were discovered:

Improper parsing of nested tags:

<s <onmouseover="alert(1)"> <;s onmouseover="alert(1)">This is a test</s>

Incomplete filtering of javascript: URIs:

<a href="javascriptJ a V a S c R iPt::alert(1)" "<s>">test</a>

UI Redressing:

<div style="z-index: 9999999; background-color: green; width: 100%; height: 100%">
<h1>You have won</h1>Please click the link and enter your login details:
<a href="http://example.com/">http://good.com</a>
</div>

Bypass via Nested Forbidden Strings:

<scrRedirecRedirect 302t 302ipt type="text/javascript">prompt(1);</scrRedirecRedirect 302t 302ipt>

Additional bypasses were discovered by Krzysztof Kotowicz in 2012 when auditing CodeIgniter's XSS filtering function, which this code was based off of.

Remediation

If you are a developer currently using the xss filter function from the validator package, you should consider replacing it with the escape filter function from the same package. This function replaces all instances of angle brackets (<, >), ampersands, and quotation marks, so no HTML tags will be processed.

References

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: sails@0.0.0-2 > sequelize@1.5.0-beta-2 > moment@1.1.1

Overview

moment is a lightweight JavaScript date library for parsing, validating, manipulating, and formatting dates.

Affected versions of this package are vulnerable to Regular expression Denial of Service (ReDoS) attacks. It used a regular expression (/[0-9]*['a-z\u00A0-\u05FF\u0700-\uD7FF\uF900-\uFDCF\uFDF0-\uFFEF]+|[\u0600-\u06FF\/]+(\s*?[\u0600-\u06FF]+){1,2}/i) in order to parse dates specified as strings. This can cause a very low impact of about 2 seconds matching time for data 50k characters long.

Details

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 moment to version 2.19.3 or higher.

References

Uninitialized Memory Exposure

low severity

Detailed paths

  • Introduced through: sails@0.0.0-2 > sequelize@1.5.0-beta-2 > mysql@0.9.6

Overview

mysql is a node.js driver for mysql.

Affected versions of the package are vulnerable due to the unsafe use of the Buffer() method. Uninitialized memory may be exposed when a value of type number is provided to various methods in mysql which require allocation of buffers and results in concatenation of uninitialized memory to the buffer collection.

This vulnerability is unlikely to be exploited, but may be possible if a server-side mysql accepts typed input for passwords from the client even though the user doesn’t control the server-side code (i.e through JSON format).

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');

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

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

Remediation

Upgrade mysql to version 2.14.0 or higher.

References

Regular Expression Denial of Service (ReDoS)

medium severity

Detailed paths

  • Introduced through: sails@0.0.0-2 > sequelize@1.5.0-beta-2 > moment@1.1.1

Overview

moment is a lightweight JavaScript date library for parsing, validating, manipulating, and formatting dates.

Affected versions of the package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks for any locale that has separate format and standalone options and format input can be controlled by the user.

An attacker can provide a specially crafted input to the format 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).

Disclosure Timeline

  • October 19th, 2016 - Reported the issue to package owner.
  • October 19th, 2016 - Issue acknowledged by package owner.
  • October 24th, 2016 - Issue fixed and version 2.15.2 released.

References

Regular Expression Denial of Service (ReDoS)

low severity

Detailed paths

  • Introduced through: sails@0.0.0-2 > sequelize@1.5.0-beta-2 > moment@1.1.1

Overview

moment is a lightweight JavaScript date library for parsing, validating, manipulating, and formatting dates.

An attacker can provide a long value to the duration 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).

"The Regular expression Denial of Service (ReDoS) is a Denial of Service attack, that exploits the fact that most Regular Expression implementations may reach extreme situations that cause them to work very slowly (exponentially related to input size). An attacker can then cause a program using a Regular Expression to enter these extreme situations and then hang for a very long time." 1

Remediation

Upgrade moment to version 2.11.2 or greater.

References