ionic@1.6.5

A tool for creating and developing Ionic Framework mobile apps.

Known vulnerabilities18
Vulnerable paths111
Dependencies813

Command Injection

high severity
  • Vulnerable module: shell-quote
  • Introduced through: ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 cordova-js@4.0.0 browserify@10.1.3 shell-quote@0.0.1

Overview

shell-quote is an npm package used to quote and parse shell commands. The quote function does not properly escape the following special characters <, >, ;, {, } , and as a result can be used by an attacker to inject malicious shell commands or leak sensitive information.

Shell command injection proof of concept

Consider the following poc.js application

var quote = require('shell-quote').quote;
            var exec = require('child_process').exec;
            
            var userInput = process.argv[2];
            
            var safeCommand = quote(['echo', userInput]);
            
            exec(safeCommand, function (err, stdout, stderr) {
              console.log(stdout);
            });
            

Running the following command will not only print the character a as expected, but will also run the another command, i.e touch malicious.sh

$ node poc.js 'a;{touch,malicious.sh}'
            

Remediation

Upgrade shell-quote to version 1.6.1 or greater.

References

Command Injection

high severity
  • Vulnerable module: shelljs
  • Introduced through: shelljs@0.2.6 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 shelljs@0.2.6
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 shelljs@0.2.6
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 shelljs@0.3.0

Overview

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.

Remediation

There is no fix version for shelljs.

References

Prototype Override Protection Bypass

high severity
  • Vulnerable module: qs
  • Introduced through: request@2.51.0, ionic-app-lib@0.3.9 and others

Detailed paths

  • Introduced through: ionic@1.6.5 request@2.51.0 qs@2.3.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 request@2.51.0 qs@2.3.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 request@2.47.0 qs@2.3.3
  • Introduced through: ionic@1.6.5 tiny-lr-fork@0.0.5 qs@0.5.6
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 tiny-lr-fork@0.0.5 qs@0.5.6
  • Introduced through: ionic@1.6.5 npm@2.1.3 request@2.44.0 qs@1.2.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 request@2.44.0 qs@1.2.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 request@2.21.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
            

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

Regular Expression Denial of Service

high severity
  • Vulnerable module: minimatch
  • Introduced through: npm@2.1.3, ionic-app-lib@0.3.9 and others

Detailed paths

  • Introduced through: ionic@1.6.5 npm@2.1.3 minimatch@1.0.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 minimatch@1.0.0
  • Introduced through: ionic@1.6.5 npm@2.1.3 glob@4.0.6 minimatch@1.0.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 glob@4.0.6 minimatch@1.0.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 glob@4.0.6 minimatch@1.0.0
  • Introduced through: ionic@1.6.5 npm@2.1.3 node-gyp@1.0.3 minimatch@1.0.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 node-gyp@1.0.3 minimatch@1.0.0
  • Introduced through: ionic@1.6.5 vinyl-fs@0.3.7 glob-stream@3.1.18 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 gulp@3.8.8 vinyl-fs@0.3.14 glob-stream@3.1.18 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 vinyl-fs@1.0.0 glob-stream@4.1.1 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 npm@2.1.3 init-package-json@1.1.3 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 init-package-json@1.1.3 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 npm@2.1.3 read-package-json@1.2.7 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 read-package-json@1.2.7 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 npm@2.1.3 node-gyp@1.0.3 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 node-gyp@1.0.3 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 vinyl-fs@0.3.7 glob-stream@3.1.18 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 gulp@3.8.8 vinyl-fs@0.3.14 glob-stream@3.1.18 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 vinyl-fs@1.0.0 glob-stream@4.1.1 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 cordova-js@4.0.0 browserify@10.1.3 glob@4.5.3 minimatch@2.0.10
  • Introduced through: ionic@1.6.5 gulp@3.8.8 liftoff@0.12.1 findup-sync@0.1.3 glob@3.2.11 minimatch@0.3.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 archiver@0.5.2 file-utils@0.1.5 findup-sync@0.1.3 glob@3.2.11 minimatch@0.3.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 archiver@0.5.2 file-utils@0.1.5 glob@3.2.11 minimatch@0.3.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 glob@3.2.11 minimatch@0.3.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 node-gyp@0.10.10 glob@3.2.11 minimatch@0.3.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 read-package-json@1.1.9 glob@3.2.11 minimatch@0.3.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 archiver@0.5.2 file-utils@0.1.5 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 vinyl-fs@0.3.7 glob-watcher@0.0.6 gaze@0.5.2 globule@0.1.0 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 gulp@3.8.8 vinyl-fs@0.3.14 glob-watcher@0.0.6 gaze@0.5.2 globule@0.1.0 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 vinyl-fs@1.0.0 glob-watcher@0.0.8 gaze@0.5.2 globule@0.1.0 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 vinyl-fs@0.3.7 glob-watcher@0.0.6 gaze@0.5.2 globule@0.1.0 glob@3.1.21 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 gulp@3.8.8 vinyl-fs@0.3.14 glob-watcher@0.0.6 gaze@0.5.2 globule@0.1.0 glob@3.1.21 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 vinyl-fs@1.0.0 glob-watcher@0.0.8 gaze@0.5.2 globule@0.1.0 glob@3.1.21 minimatch@0.2.14
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 node-gyp@0.10.10 minimatch@0.4.0

Overview

minimatch is a minimalistic matching library used for converting glob expressions into JavaScript RegExp objects.

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).

"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 minimatch to version 3.0.2 or greater.

References

Symlink Arbitrary File Overwrite

high severity
  • Vulnerable module: tar
  • Introduced through: npm@2.1.3 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 npm@2.1.3 tar@1.0.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 tar@1.0.3
  • Introduced through: ionic@1.6.5 npm@2.1.3 node-gyp@1.0.3 tar@1.0.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 node-gyp@1.0.3 tar@1.0.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 tar@1.0.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 tar@0.1.20
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 node-gyp@0.10.10 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

npm Token Leak

high severity
  • Vulnerable module: npm
  • Introduced through: npm@2.1.3 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 npm@2.1.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4

Overview

This vulnerability could cause the unintentional leakage of bearer tokens. A design flaw in npm's registry allows an attacker to set up an HTTP server that could collect authentication information, and then use this authentication information to impersonate the users whose tokens they collected. The attacker could do anything the compromised users could do, including publishing new versions of packages.

Details

The primary npm registry has, since late 2014, used HTTP bearer tokens to authenticate requests from the npm command-line interface. Due to a design flaw in the CLI, these bearer tokens were sent with every request made by logged-in users, regardless of the destination of the request. (The bearers only should have been included for requests made against a registry or registries used for the current install.)

This flaw allows an attacker to set up an HTTP server that could collect authentication information. They could then use this information to impersonate the users whose tokens they collected. This impersonation would allow them to do anything the compromised users could do, including publishing new versions of packages.

With the fixes npm have released, the CLI will only send bearer tokens with requests made against a registry. npm’s CLI team believe that the fix won’t break any existing registry setups. However, it’s possible the change will be breaking in some cases, due to the large number of registry software suites used.

Remediation

  1. Upgrade npm to ">= 3.8.3 || >= 2.15.1"
  2. Invalidate your current npm bearer tokens

References

Denial of Service (Event Loop Blocking)

medium severity
  • Vulnerable module: qs
  • Introduced through: tiny-lr-fork@0.0.5 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 tiny-lr-fork@0.0.5 qs@0.5.6
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 tiny-lr-fork@0.0.5 qs@0.5.6
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 request@2.21.0 qs@0.6.6

Overview

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

https://nodesecurity.io/advisories/28

Denial of Service (Memory Exhaustion)

medium severity
  • Vulnerable module: qs
  • Introduced through: tiny-lr-fork@0.0.5 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 tiny-lr-fork@0.0.5 qs@0.5.6
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 tiny-lr-fork@0.0.5 qs@0.5.6
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 request@2.21.0 qs@0.6.6

Overview

During parsing, the qs module may create a sparse area (an array where not 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

Remote Memory Exposure

medium severity
  • Vulnerable module: request
  • Introduced through: request@2.51.0, ionic-app-lib@0.3.9 and others

Detailed paths

  • Introduced through: ionic@1.6.5 request@2.51.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 request@2.51.0
  • Introduced through: ionic@1.6.5 npm@2.1.3 request@2.44.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 request@2.44.0
  • Introduced through: ionic@1.6.5 prompt@0.2.12 winston@0.6.2 request@2.9.203
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 prompt@0.2.12 winston@0.6.2 request@2.9.203
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 request@2.47.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 request@2.21.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

Root Path Disclosure

medium severity
  • Vulnerable module: send
  • Introduced through: serve-static@1.7.1 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 serve-static@1.7.1 send@0.10.1
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 serve-static@1.7.1 send@0.10.1

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

Uninitialized Memory Exposure

medium severity
  • Vulnerable module: concat-stream
  • Introduced through: ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 cordova-js@4.0.0 browserify@10.1.3 concat-stream@1.4.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 cordova-js@4.0.0 browserify@10.1.3 insert-module-globals@6.6.3 concat-stream@1.4.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 cordova-js@4.0.0 browserify@10.1.3 browser-pack@4.0.4 concat-stream@1.4.10
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 cordova-js@4.0.0 browserify@10.1.3 module-deps@3.9.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 concatination 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

Unsigned Request Headers

medium severity
  • Vulnerable module: http-signature
  • Introduced through: ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 request@2.21.0 http-signature@0.9.11

Overview

http-signature is a Reference implementation of Joyent's HTTP Signature scheme. Affected versions of the package are vulnerable to header forgery, due to the header names not being signed. An attacker could switch the header list order and header value order ending up wit the same signature for two separate requests.

Remediation

Upgrade http-signature to version 0.10.0 or higher.

References

semver Regular Expression Denial of Service

medium severity
  • Vulnerable module: semver
  • Introduced through: gulp@3.8.8, npm@2.1.3 and others

Detailed paths

  • Introduced through: ionic@1.6.5 gulp@3.8.8 semver@3.0.1
  • Introduced through: ionic@1.6.5 npm@2.1.3 semver@4.0.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 semver@4.0.3
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 semver@2.1.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 semver@2.0.11
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npmconf@0.1.16 semver@2.3.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 read-package-json@1.1.9 normalize-package-data@0.2.13 semver@2.3.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 read-installed@0.2.5 semver@2.3.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 npmconf@0.1.16 semver@2.3.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 node-gyp@0.10.10 semver@2.1.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 npm-registry-client@0.2.31 semver@2.3.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 init-package-json@0.0.10 semver@2.3.2

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

Insecure Randomness

low severity
  • Vulnerable module: node-uuid
  • Introduced through: ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 xcode@0.6.7 node-uuid@1.3.3

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

Open Redirect

low severity
  • Vulnerable module: serve-static
  • Introduced through: serve-static@1.7.1 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 serve-static@1.7.1
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 serve-static@1.7.1

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

Regular Expression Denial of Service

low severity
  • Vulnerable module: hawk
  • Introduced through: request@2.51.0, ionic-app-lib@0.3.9 and others

Detailed paths

  • Introduced through: ionic@1.6.5 request@2.51.0 hawk@1.1.1
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 request@2.51.0 hawk@1.1.1
  • Introduced through: ionic@1.6.5 npm@2.1.3 request@2.44.0 hawk@1.1.1
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 npm@2.1.3 request@2.44.0 hawk@1.1.1
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 request@2.47.0 hawk@1.1.1
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 ionic-cordova-lib@5.1.7 npm@1.3.4 request@2.21.0 hawk@0.13.1

Overview

A Regular expression Denial of Service (ReDoS) vulnerability exists in hawk package, affecting version 4.1.0 and below.

"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

References

Regular Expression Denial of Service

low severity
  • Vulnerable module: ms
  • Introduced through: connect@3.1.1, ionic-app-lib@0.3.9 and others

Detailed paths

  • Introduced through: ionic@1.6.5 connect@3.1.1 debug@1.0.4 ms@0.6.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 connect@3.1.1 debug@1.0.4 ms@0.6.2
  • Introduced through: ionic@1.6.5 connect@3.1.1 finalhandler@0.1.0 debug@1.0.4 ms@0.6.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 connect@3.1.1 finalhandler@0.1.0 debug@1.0.4 ms@0.6.2
  • Introduced through: ionic@1.6.5 finalhandler@0.2.0 debug@2.0.0 ms@0.6.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 finalhandler@0.2.0 debug@2.0.0 ms@0.6.2
  • Introduced through: ionic@1.6.5 serve-static@1.7.1 send@0.10.1 ms@0.6.2
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 serve-static@1.7.1 send@0.10.1 ms@0.6.2
  • Introduced through: ionic@1.6.5 serve-static@1.7.1 send@0.10.1 debug@2.1.3 ms@0.7.0
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 serve-static@1.7.1 send@0.10.1 debug@2.1.3 ms@0.7.0

Overview

The Regular expression Denial of Service (ReDoS) vulnerability exists in the ms package, affecting version 0.7.0 and below.

Details

ms is a milliseconds conversion utility, used to convert a time period string (i.e. "2 days", "1h") into milliseconds integer. The regular expression used by the function to parse the time is vulnerable to a denial of service attack, where extremely long strings passed to ms() can take a long time to process, subsequently blocking the event loop for that extended period.

"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 ms to version 0.7.1.

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

References

Root Path Disclosure

low severity
  • Vulnerable module: serve-static
  • Introduced through: serve-static@1.7.1 and ionic-app-lib@0.3.9

Detailed paths

  • Introduced through: ionic@1.6.5 serve-static@1.7.1
  • Introduced through: ionic@1.6.5 ionic-app-lib@0.3.9 serve-static@1.7.1

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: