mean A fullstack JavaScript framework powered by MongoDB, ExpressJS, AngularJS, NodeJS.

Known vulnerabilities2
Vulnerable paths3

Command Injection

high severity
  • Vulnerable module: shelljs
  • Introduced through: shelljs@0.7.7 and meanio@0.9.4

Detailed paths

  • Introduced through: mean@linnovate/mean#0e412bec9313ef60248d5f8016e247aede8782dd shelljs@0.7.7
  • Introduced through: mean@linnovate/mean#0e412bec9313ef60248d5f8016e247aede8782dd meanio@0.9.4 shelljs@0.7.7


shelljs is a portable Unix shell commands for Node.js. It is possible to invoke commands from shell.exec() from external sources, allowing an attacker to inject arbitrary commands.


There is no fix version for shelljs.


Prototype Override Protection Bypass

high severity
  • Vulnerable module: qs
  • Introduced through: connect-modrewrite@0.9.0

Detailed paths

  • Introduced through: mean@linnovate/mean#0e412bec9313ef60248d5f8016e247aede8782dd connect-modrewrite@0.9.0 qs@1.2.2


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.


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


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.


Regular Expression Denial of Service (DoS)

Vulnerability patched for: meanio@0.9.4.

medium severity
  • Vulnerable module: uglify-js
  • Introduced through: meanio@0.9.4

Detailed paths

  • Introduced through: mean@linnovate/mean#0e412bec9313ef60248d5f8016e247aede8782dd meanio@0.9.4 swig@1.4.2 uglify-js@2.4.24


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.


"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


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