Skip to main content

Test Results

sonyccd/resume

Vulnerabilities

 71 via 548 paths

Dependencies

 899

Source

 GitHub

Commit

 f01c3b42

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Issue type
  • 71
  • 1
Severity
  • 1
  • 30
  • 37
  • 4
Status
  • 71
  • 1
  • 0

critical severity

Improper Input Validation

  • Vulnerable module: xmldom
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3 › xmldom@0.1.31

Overview

xmldom is an A pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module.

Affected versions of this package are vulnerable to Improper Input Validation due to parsing XML that is not well-formed, and contains multiple top-level elements. All the root nodes are being added to the childNodes collection of the Document, without reporting or throwing any error.

Workarounds

One of the following approaches might help, depending on your use case:

  1. Instead of searching for elements in the whole DOM, only search in the documentElement.

  2. Reject a document with a document that has more than 1 childNode.

PoC

var DOMParser = require('xmldom').DOMParser;
var xmlData = '<?xml version="1.0" encoding="UTF-8"?>\n' +
'<root>\n' +
'  <branch girth="large">\n' +
'    <leaf color="green" />\n' +
'  </branch>\n' +
'</root>\n' +
'<root>\n' +
'  <branch girth="twig">\n' +
'    <leaf color="gold" />\n' +
'  </branch>\n' +
'</root>\n';
var xmlDOM = new DOMParser().parseFromString(xmlData);
console.log(xmlDOM.toString());

This will result with the following output:

<?xml version="1.0" encoding="UTF-8"?><root>
  <branch girth="large">
    <leaf color="green"/>
  </branch>
</root>
<root>
  <branch girth="twig">
    <leaf color="gold"/>
  </branch>
</root>

Remediation

There is no fixed version for xmldom.

References

Improper Input Validation vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to NULL Pointer Dereference in the function Sass::Functions::selector_append which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact. node-sass is affected by this vulnerability due to its bundled usage of libsass.

Remediation

There is no fixed version for node-sass.

References

NULL Pointer Dereference vulnerability report

high severity

Use After Free

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Use After Free via the SharedPtr class in SharedPtr.cpp (or SharedPtr.hpp) that may cause a denial of service (application crash) or possibly have unspecified other impact. Note: node-sass is affected by this vulnerability due to its bundled usage of the libsass package.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

There is no fixed version for node-sass.

References

Use After Free vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: cross-spawn
  • Introduced through: gulp-imagemin@4.1.0, node-sass@4.14.1 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › exec-buffer@3.2.0 › execa@0.7.0 › cross-spawn@5.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › exec-buffer@3.2.0 › execa@0.7.0 › cross-spawn@5.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › exec-buffer@3.2.0 › execa@0.7.0 › cross-spawn@5.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › cross-spawn@3.0.1
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › cross-spawn@3.0.1
    Remediation: Upgrade to gulp-sass@5.0.0.

…and 2 more

Overview

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper input sanitization. An attacker can increase the CPU usage and crash the program by crafting a very large and well crafted string.

PoC

const { argument } = require('cross-spawn/lib/util/escape');
var str = "";
for (var i = 0; i < 1000000; i++) {
  str += "\\";
}
str += "◎";

console.log("start")
argument(str)
console.log("end")

// run `npm install cross-spawn` and `node attack.js` 
// then the program will stuck forever with high CPU usage

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 cross-spawn to version 6.0.6, 7.0.5 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: jspdf
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3
    Remediation: Upgrade to jspdf@3.0.1.

Overview

jspdf is a PDF Document creation from JavaScript

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in the addImage(), html(), and addSvgAsImage() methods. An attacker can occupy excessive CPU by supplying a malicious data-url.

PoC

import { jsPDF } from "jpsdf" 

const doc = new jsPDF();
const payload = 'data:/charset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=scharset=s\x00base64,undefined';

const startTime = performance.now()

try {
 doc.addImage(payload, "PNG", 10, 40, 180, 180, undefined, "SLOW");
} catch (err) {
  const endTime = performance.now()
  console.log(`Call to doc.addImage took ${endTime - startTime} milliseconds`)
}

doc.save("a4.pdf");

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 jspdf to version 3.0.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Arbitrary File Write

  • Vulnerable module: tar
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.

This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both \ and / characters as path separators. However, \ is a valid filename character on posix systems.

By first creating a directory, and then replacing that directory with a symlink, it is possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location. This can lead to extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite.

Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at FOO, followed by a symbolic link named foo, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but not from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the FOO directory would then be placed in the target of the symbolic link, thinking that the directory had already been created.

Remediation

Upgrade tar to version 6.1.7, 5.0.8, 4.4.16 or higher.

References

Arbitrary File Write vulnerability report

high severity

Arbitrary File Write

  • Vulnerable module: tar
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.

This logic is insufficient when extracting tar files that contain two directories and a symlink with names containing unicode values that normalized to the same value. Additionally, on Windows systems, long path portions would resolve to the same file system entities as their 8.3 "short path" counterparts. A specially crafted tar archive can include directories with two forms of the path that resolve to the same file system entity, followed by a symbolic link with a name in the first form, lastly followed by a file using the second form. This leads to bypassing node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and extracting arbitrary files into that location.

Remediation

Upgrade tar to version 6.1.9, 5.0.10, 4.4.18 or higher.

References

Arbitrary File Write vulnerability report

high severity

Arbitrary File Write

  • Vulnerable module: tar
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Write. node-tar aims to guarantee that any file whose location would be outside of the extraction target directory is not extracted. This is, in part, accomplished by sanitizing absolute paths of entries within the archive, skipping archive entries that contain .. path portions, and resolving the sanitized paths against the extraction target directory.

This logic is insufficient on Windows systems when extracting tar files that contain a path that is not an absolute path, but specify a drive letter different from the extraction target, such as C:some\path. If the drive letter does not match the extraction target, for example D:\extraction\dir, then the result of path.resolve(extractionDirectory, entryPath) resolves against the current working directory on the C: drive, rather than the extraction target directory.

Additionally, a .. portion of the path can occur immediately after the drive letter, such as C:../foo, and is not properly sanitized by the logic that checks for .. within the normalized and split portions of the path.

Note: This only affects users of node-tar on Windows systems.

Remediation

Upgrade tar to version 6.1.9, 5.0.10, 4.4.18 or higher.

References

Arbitrary File Write vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: xmldom
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3 › xmldom@0.1.31

Overview

xmldom is an A pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module.

Affected versions of this package are vulnerable to Prototype Pollution through the copy() function in dom.js. Exploiting this vulnerability is possible via the p variable.

DISPUTED This vulnerability has been disputed by the maintainers of the package. Currently the only viable exploit that has been demonstrated is to pollute the target object (rather then the global object which is generally the case for Prototype Pollution vulnerabilities) and it is yet unclear if this limited attack vector exposes any vulnerability in the context of this package.

See the linked GitHub Issue for full details on the discussion around the legitimacy and potential revocation of this vulnerability.

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

There is no fixed version for xmldom.

References

Prototype Pollution vulnerability report

high severity

Arbitrary File Overwrite

  • Vulnerable module: tar
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Overwrite. This is due to insufficient symlink protection. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created.

This logic is insufficient when extracting tar files that contain both a directory and a symlink with the same name as the directory. This order of operations results in the directory being created and added to the node-tar directory cache. When a directory is present in the directory cache, subsequent calls to mkdir for that directory are skipped. However, this is also where node-tar checks for symlinks occur. By first creating a directory, and then replacing that directory with a symlink, it is possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location.

Remediation

Upgrade tar to version 3.2.3, 4.4.15, 5.0.7, 6.1.2 or higher.

References

Arbitrary File Overwrite vulnerability report

high severity

Arbitrary File Overwrite

  • Vulnerable module: tar
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Arbitrary File Overwrite. This is due to insufficient absolute path sanitization.

node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservePaths flag is not set to true. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example, the path /home/user/.bashrc would turn into home/user/.bashrc.

This logic is insufficient when file paths contain repeated path roots such as ////home/user/.bashrc. node-tar only strips a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. ///home/user/.bashrc) still resolves to an absolute path.

Remediation

Upgrade tar to version 3.2.2, 4.4.14, 5.0.6, 6.1.1 or higher.

References

Arbitrary File Overwrite vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: canvg
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3
    Remediation: Upgrade to jspdf@2.0.0.

Overview

canvg is a JavaScript SVG parser and renderer on Canvas.

Affected versions of this package are vulnerable to Prototype Pollution in the StyleElement constructor.

PoC


(async () => {
  // Assuming import is set up properly
  import { StyleElement } from 'canvg';

  // Output expected: "No output before attack"
  console.log({}.polluted); 

  // Attacker-controlled CSS input
  const maliciousCSS = `
  __proto__ { polluted: "Yes, polluted!"; }
  `;

  // Creating a mock document object
  const fakeDocument = {
    styles: {},
    stylesSpecificity: {},
    addEventListener: () => {},
    createElement: () => ({ style: {} }),
    appendChild: () => {}
  };

  // Creating a mock node object
  const fakeNode = {
    childNodes: [{
        textContent: maliciousCSS
    }]
  };

  // Instantiating StyleElement to simulate the attack
  const se = new StyleElement(fakeDocument, fakeNode);

  // Verifying if the prototype pollution was successful
  console.log({}.polluted);  // Expected output: "Yes, polluted!"
})();

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade canvg to version 3.0.11, 4.0.3 or higher.

References

Prototype Pollution vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: ansi-regex
  • Introduced through: gulp@3.9.1, gulp-plumber@1.2.1 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-plumber@1.2.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-plumber@1.2.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.1.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.1.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › logalot@2.1.0 › squeak@1.3.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tarbz2@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-targz@3.1.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-unzip@3.4.0 › strip-dirs@1.1.1 › sum-up@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1

…and 233 more

Overview

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to the sub-patterns [[\\]()#;?]* and (?:;[-a-zA-Z\\d\\/#&.:=?%@~_]*)*.

PoC

import ansiRegex from 'ansi-regex';

for(var i = 1; i <= 50000; i++) {
    var time = Date.now();
    var attack_str = "\u001B["+";".repeat(i*10000);
    ansiRegex().test(attack_str)
    var time_cost = Date.now() - time;
    console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
}

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 ansi-regex to version 3.0.1, 4.1.1, 5.0.1, 6.0.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Excessive Platform Resource Consumption within a Loop

  • Vulnerable module: braces
  • Introduced through: gulp@3.9.1, jpegtran-bin@3.2.0 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › liftoff@2.5.0 › findup-sync@2.0.0 › micromatch@3.1.10 › braces@2.3.2
    Remediation: Upgrade to gulp@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5

…and 18 more

Overview

braces is a Bash-like brace expansion, implemented in JavaScript.

Affected versions of this package are vulnerable to Excessive Platform Resource Consumption within a Loop due improper limitation of the number of characters it can handle, through the parse function. An attacker can cause the application to allocate excessive memory and potentially crash by sending imbalanced braces as input.

PoC

const { braces } = require('micromatch');

console.log("Executing payloads...");

const maxRepeats = 10;

for (let repeats = 1; repeats <= maxRepeats; repeats += 1) {
  const payload = '{'.repeat(repeats*90000);

  console.log(`Testing with ${repeats} repeats...`);
  const startTime = Date.now();
  braces(payload);
  const endTime = Date.now();
  const executionTime = endTime - startTime;
  console.log(`Regex executed in ${executionTime / 1000}s.\n`);
}

Remediation

Upgrade braces to version 3.0.3 or higher.

References

Excessive Platform Resource Consumption within a Loop vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

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

Affected versions of this package are vulnerable to Prototype Pollution through the zipObjectDeep function due to improper user input sanitization in the baseZipObject function.

PoC

lodash.zipobjectdeep:

const zipObjectDeep = require("lodash.zipobjectdeep");

let emptyObject = {};


console.log(`[+] Before prototype pollution : ${emptyObject.polluted}`);
//[+] Before prototype pollution : undefined

zipObjectDeep(["constructor.prototype.polluted"], [true]);
//we inject our malicious attributes in the vulnerable function

console.log(`[+] After prototype pollution : ${emptyObject.polluted}`);
//[+] After prototype pollution : true

lodash:

const test = require("lodash");

let emptyObject = {};


console.log(`[+] Before prototype pollution : ${emptyObject.polluted}`);
//[+] Before prototype pollution : undefined

test.zipObjectDeep(["constructor.prototype.polluted"], [true]);
//we inject our malicious attributes in the vulnerable function

console.log(`[+] After prototype pollution : ${emptyObject.polluted}`);
//[+] After prototype pollution : true

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade lodash to version 4.17.17 or higher.

References

Prototype Pollution vulnerability report

high severity

Inefficient Regular Expression Complexity

  • Vulnerable module: micromatch
  • Introduced through: gulp@3.9.1, jpegtran-bin@3.2.0 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › liftoff@2.5.0 › findup-sync@2.0.0 › micromatch@3.1.10
    Remediation: Upgrade to gulp@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11

…and 18 more

Overview

Affected versions of this package are vulnerable to Inefficient Regular Expression Complexity due to the use of unsafe pattern configurations that allow greedy matching through the micromatch.braces() function. An attacker can cause the application to hang or slow down by passing a malicious payload that triggers extensive backtracking in regular expression processing.

Remediation

Upgrade micromatch to version 4.0.8 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: minimatch
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-stream@3.1.18 › minimatch@2.0.10
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-stream@3.1.18 › glob@4.5.3 › minimatch@2.0.10
    Remediation: Upgrade to gulp@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › minimatch@0.2.14
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › 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

…and 1 more

Overview

minimatch is a minimal matching utility.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via complicated and illegal regexes.

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

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: nth-check
  • Introduced through: gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-svgo@6.0.0 › svgo@1.3.2 › css-select@2.1.0 › nth-check@1.0.2
    Remediation: Upgrade to gulp-imagemin@8.0.0.

Overview

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) when parsing crafted invalid CSS nth-checks, due to the sub-pattern \s*(?:([+-]?)\s*(\d+))? in RE_NTH_ELEMENT with quantified overlapping adjacency.

PoC

var nthCheck = require("nth-check")
for(var i = 1; i <= 50000; i++) {
    var time = Date.now();
    var attack_str = '2n' + ' '.repeat(i*10000)+"!";
    try {
        nthCheck.parse(attack_str) 
    }
    catch(err) {
        var time_cost = Date.now() - time;
        console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
    }
}

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 nth-check to version 2.0.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: semver
  • Introduced through: gulp@3.9.1, jpegtran-bin@3.2.0 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › semver@4.3.6
    Remediation: Upgrade to gulp@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › semver@4.3.6
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › semver@4.3.6
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › semver@4.3.6
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › semver@4.3.6
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › semver@5.3.0
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › semver@5.3.0
    Remediation: Upgrade to gulp-sass@5.0.0.

…and 4 more

Overview

semver is a semantic version parser used by npm.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

PoC


const semver = require('semver')
const lengths_2 = [2000, 4000, 8000, 16000, 32000, 64000, 128000]

console.log("n[+] Valid range - Test payloads")
for (let i = 0; i =1.2.3' + ' '.repeat(lengths_2[i]) + '<1.3.0';
const start = Date.now()
semver.validRange(value)
// semver.minVersion(value)
// semver.maxSatisfying(["1.2.3"], value)
// semver.minSatisfying(["1.2.3"], value)
// new semver.Range(value, {})

const end = Date.now();
console.log('length=%d, time=%d ms', value.length, end - start);
}

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 semver to version 5.7.2, 6.3.1, 7.5.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: semver-regex
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0

…and 1 more

Overview

semver-regex is a Regular expression for matching semver versions

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). This can occur when running the regex on untrusted user input in a server context.

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 semver-regex to version 4.0.1, 3.1.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: semver-regex
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0

…and 1 more

Overview

semver-regex is a Regular expression for matching semver versions

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). semverRegex function contains a regex that allows exponential backtracking.

PoC

import semverRegex from 'semver-regex';

// The following payload would take excessive CPU cycles
var payload = '0.0.0-0' + '.-------'.repeat(100000) + '@';
semverRegex().test(payload);

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 semver-regex to version 3.1.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: trim-newlines
  • Introduced through: node-sass@4.14.1, gulp-sass@3.2.1 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › meow@3.7.0 › trim-newlines@1.0.0
    Remediation: Upgrade to node-sass@6.0.1.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › meow@3.7.0 › trim-newlines@1.0.0
    Remediation: Upgrade to gulp-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-check@2.0.0 › executable@1.1.0 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › logalot@2.1.0 › squeak@1.3.0 › lpad-align@1.1.2 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › meow@3.7.0 › trim-newlines@1.0.0
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › bin-check@2.0.0 › executable@1.1.0 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-check@2.0.0 › executable@1.1.0 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › bin-check@2.0.0 › executable@1.1.0 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › logalot@2.1.0 › squeak@1.3.0 › lpad-align@1.1.2 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › logalot@2.1.0 › squeak@1.3.0 › lpad-align@1.1.2 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › logalot@2.1.0 › squeak@1.3.0 › lpad-align@1.1.2 › meow@3.7.0 › trim-newlines@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › meow@3.7.0 › trim-newlines@1.0.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › meow@3.7.0 › trim-newlines@1.0.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › meow@3.7.0 › trim-newlines@1.0.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.

…and 11 more

Overview

trim-newlines is a Trim newlines from the start and/or end of a string

Affected versions of this package are vulnerable to Denial of Service (DoS) via the end() method.

Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

  • High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

  • Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm ws package

Remediation

Upgrade trim-newlines to version 3.0.1, 4.0.1 or higher.

References

Denial of Service (DoS) vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: unset-value
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › liftoff@2.5.0 › findup-sync@2.0.0 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › liftoff@2.5.0 › findup-sync@2.0.0 › micromatch@3.1.10 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › liftoff@2.5.0 › findup-sync@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › liftoff@2.5.0 › findup-sync@2.0.0 › micromatch@3.1.10 › nanomatch@1.2.13 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › liftoff@2.5.0 › findup-sync@2.0.0 › micromatch@3.1.10 › extglob@2.0.4 › expand-brackets@2.1.4 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0

…and 2 more

Overview

Affected versions of this package are vulnerable to Prototype Pollution via the unset function in index.js, because it allows access to object prototype properties.

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade unset-value to version 2.0.1 or higher.

References

Prototype Pollution vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: url-regex
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › url-regex@3.2.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › url-regex@3.2.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › url-regex@3.2.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › url-regex@3.2.0

…and 1 more

Overview

url-regex is a package with regular expression for matching URLs

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). An attacker providing a very long string in String.test can cause a Denial of Service.

PoC by Nick Baugh

For url-regex package:

 require('url-regex')({ strict: false }).test('018137.113.215.4074.138.129.172220.179.206.94180.213.144.175250.45.147.1364868726sgdm6nohQ')

For urlregex package:

require('urlregex')({ strict: false }).test('018137.113.215.4074.138.129.172220.179.206.94180.213.144.175250.45.147.1364868726sgdm6nohQ')

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

There is no fixed version for url-regex.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

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

Affected versions of this package are vulnerable to Prototype Pollution. The function defaultsDeep could be tricked into adding or modifying properties of Object.prototype using a constructor payload.

PoC by Snyk

const mergeFn = require('lodash').defaultsDeep;
const payload = '{"constructor": {"prototype": {"a0": true}}}'

function check() {
    mergeFn({}, JSON.parse(payload));
    if (({})[`a0`] === true) {
        console.log(`Vulnerable to Prototype Pollution via ${payload}`);
    }
  }

check();

For more information, check out our blog post

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade lodash to version 4.17.12 or higher.

References

Prototype Pollution vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

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

Affected versions of this package are vulnerable to Prototype Pollution via the set and setwith functions due to improper user input sanitization.

PoC

lod = require('lodash')
lod.set({}, "__proto__[test2]", "456")
console.log(Object.prototype)

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade lodash to version 4.17.17 or higher.

References

Prototype Pollution vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

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

Affected versions of this package are vulnerable to Prototype Pollution. The functions merge, mergeWith, and defaultsDeep could be tricked into adding or modifying properties of Object.prototype. This is due to an incomplete fix to CVE-2018-3721.

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade lodash to version 4.17.11 or higher.

References

Prototype Pollution vulnerability report

high severity

Code Injection

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

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

Affected versions of this package are vulnerable to Code Injection via template.

PoC

var _ = require('lodash');

_.template('', { variable: '){console.log(process.env)}; with(obj' })()

Remediation

Upgrade lodash to version 4.17.21 or higher.

References

Code Injection vulnerability report

high severity

Code Injection

  • Vulnerable module: lodash.template
  • Introduced through: gulp@3.9.1, gulp-sass@3.2.1 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › gulp-util@3.0.8 › lodash.template@3.6.2

…and 7 more

Overview

lodash.template is a The Lodash method _.template exported as a Node.js module.

Affected versions of this package are vulnerable to Code Injection via template.

PoC

var _ = require('lodash');

_.template('', { variable: '){console.log(process.env)}; with(obj' })()

Remediation

There is no fixed version for lodash.template.

References

Code Injection vulnerability report

high severity

Cross-site Request Forgery (CSRF)

  • Vulnerable module: axios
  • Introduced through: browser-sync@2.29.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › browser-sync@2.29.3 › localtunnel@2.0.2 › axios@0.21.4

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Cross-site Request Forgery (CSRF) due to inserting the X-XSRF-TOKEN header using the secret XSRF-TOKEN cookie value in all requests to any server when the XSRF-TOKEN0 cookie is available, and the withCredentials setting is turned on. If a malicious user manages to obtain this value, it can potentially lead to the XSRF defence mechanism bypass.

Workaround

Users should change the default XSRF-TOKEN cookie name in the Axios configuration and manually include the corresponding header only in the specific places where it's necessary.

Remediation

Upgrade axios to version 0.28.0, 1.6.0 or higher.

References

Cross-site Request Forgery (CSRF) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Denial of Service (DoS). Uncontrolled recursion is possible in Sass::Complex_Selector::perform in ast.hpp and Sass::Inspect::operator in inspect.cpp. Note: node-sass is affected by this vulnerability due to its bundled usage of the libsass package.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

There is no fixed version for node-sass.

References

Denial of Service (DoS) vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Out-of-Bounds. A heap-based buffer over-read exists in Sass::Prelexer::parenthese_scope in prelexer.hpp. node-sass is affected by this vulnerability due to its bundled usage of libsass.

Remediation

There is no fixed version for node-sass.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Out-of-Bounds via Sass::Prelexer::alternatives in prelexer.hpp. Note: node-sass is affected by this vulnerability due to its bundled usage of the libsass package.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

There is no fixed version for node-sass.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Out-of-bounds Read. The function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file. Note: node-sass is affected by this vulnerability due to its bundled usage of the libsass package.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

There is no fixed version for node-sass.

References

Out-of-bounds Read vulnerability report

medium severity

Server-side Request Forgery (SSRF)

  • Vulnerable module: request
  • Introduced through: node-sass@4.14.1, gulp-sass@3.2.1 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › request@2.88.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › request@2.88.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › request@2.88.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › request@2.88.2
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3 › jsdom@8.5.0 › request@2.88.2

…and 2 more

Overview

request is a simplified http request client.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to insufficient checks in the lib/redirect.js file by allowing insecure redirects in the default configuration, via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP).

NOTE: request package has been deprecated, so a fix is not expected. See https://github.com/request/request/issues/3142.

Remediation

A fix was pushed into the master branch but not yet published.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity

Uncontrolled Resource Consumption ('Resource Exhaustion')

  • Vulnerable module: tar
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Uncontrolled Resource Consumption ('Resource Exhaustion') due to the lack of folders count validation during the folder creation process. An attacker who generates a large number of sub-folders can consume memory on the system running the software and even crash the client within few seconds of running it using a path with too many sub-folders inside.

Remediation

Upgrade tar to version 6.2.1 or higher.

References

Uncontrolled Resource Consumption ('Resource Exhaustion') vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: tough-cookie
  • Introduced through: node-sass@4.14.1, gulp-sass@3.2.1 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › request@2.88.2 › tough-cookie@2.5.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › request@2.88.2 › tough-cookie@2.5.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › request@2.88.2 › tough-cookie@2.5.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3 › jsdom@8.5.0 › tough-cookie@2.5.0
    Remediation: Upgrade to jspdf@2.5.2.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › request@2.88.2 › tough-cookie@2.5.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3 › jsdom@8.5.0 › request@2.88.2 › tough-cookie@2.5.0

…and 3 more

Overview

tough-cookie is a RFC6265 Cookies and CookieJar module for Node.js.

Affected versions of this package are vulnerable to Prototype Pollution due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. Due to an issue with the manner in which the objects are initialized, an attacker can expose or modify a limited amount of property information on those objects. There is no impact to availability.

PoC

// PoC.js
async function main(){
var tough = require("tough-cookie");
var cookiejar = new tough.CookieJar(undefined,{rejectPublicSuffixes:false});
// Exploit cookie
await cookiejar.setCookie(
  "Slonser=polluted; Domain=__proto__; Path=/notauth",
  "https://__proto__/admin"
);
// normal cookie
var cookie = await cookiejar.setCookie(
  "Auth=Lol; Domain=google.com; Path=/notauth",
  "https://google.com/"
);

//Exploit cookie
var a = {};
console.log(a["/notauth"]["Slonser"])
}
main();

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade tough-cookie to version 4.1.3 or higher.

References

Prototype Pollution vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: xmldom
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3 › xmldom@0.1.31

Overview

xmldom is an A pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module.

Affected versions of this package are vulnerable to Improper Input Validation. It does not correctly escape special characters when serializing elements are removed from their ancestor. This may lead to unexpected syntactic changes during XML processing in some downstream applications.

Note: Customers who use "xmldom" package, should use "@xmldom/xmldom" instead, as "xmldom" is no longer maintained.

Remediation

There is no fixed version for xmldom.

References

Improper Input Validation vulnerability report

medium severity

Arbitrary File Write via Archive Extraction (Zip Slip)

  • Vulnerable module: decompress
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0

…and 9 more

Overview

decompress is a package that can be used for extracting archives.

Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip). It is possible to bypass the security measures provided by decompress and conduct ZIP path traversal through symlinks.

PoC

const decompress = require('decompress');

decompress('slip.tar.gz', 'dist').then(files => {
    console.log('done!');
});

Details

It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicous file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:


+2018-04-15 22:04:29 ..... 19 19 good.txt

+2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys

Remediation

Upgrade decompress to version 4.2.1 or higher.

References

Arbitrary File Write via Archive Extraction (Zip Slip) vulnerability report

medium severity

Arbitrary File Write via Archive Extraction (Zip Slip)

  • Vulnerable module: decompress-tar
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › decompress-tar@3.1.0

…and 9 more

Overview

decompress-tar is a tar plugin for decompress.

Affected versions of this package are vulnerable to Arbitrary File Write via Archive Extraction (Zip Slip). It is possible to bypass the security measures provided by decompress and conduct ZIP path traversal through symlinks.

PoC

const decompress = require('decompress');

decompress('slip.tar.gz', 'dist').then(files => {
    console.log('done!');
});

Details

It is exploited using a specially crafted zip archive, that holds path traversal filenames. When exploited, a filename in a malicious archive is concatenated to the target extraction directory, which results in the final path ending up outside of the target folder. For instance, a zip may hold a file with a "../../file.exe" location and thus break out of the target folder. If an executable or a configuration file is overwritten with a file containing malicious code, the problem can turn into an arbitrary code execution issue quite easily.

The following is an example of a zip archive with one benign file and one malicious file. Extracting the malicous file will result in traversing out of the target folder, ending up in /root/.ssh/ overwriting the authorized_keys file:


+2018-04-15 22:04:29 ..... 19 19 good.txt

+2018-04-15 22:04:42 ..... 20 20 ../../../../../../root/.ssh/authorized_keys

Remediation

There is no fixed version for decompress-tar.

References

Arbitrary File Write via Archive Extraction (Zip Slip) vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: jspdf
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3
    Remediation: Upgrade to jspdf@2.0.0.

Overview

jspdf is a PDF Document creation from JavaScript

Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It's possible to use <<script>script> in order to go over the filtering regex.

PoC

import jsPDF from "jspdf";

var doc = new jsPDF();

let html = `
<p id='test'>a</p>
<<script>script>document.write(window.location);</</script>script>
`;
doc.fromHTML(
  html,
  0,
  0,
  {
    width: 100 // max width of content on PDF
  },
  function(_) {
    doc.save();
  }
);

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade jspdf to version 2.0.0 or higher.

Cross-site Scripting (XSS) vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: jspdf
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3
    Remediation: Upgrade to jspdf@2.0.0.

Overview

jspdf is a PDF Document creation from JavaScript

Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It's possible to inject JavaScript code via the html method.

PoC

var doc = new jsPDF();
window.html2canvas = html2canvas;
let html = `
<p id='test'>a</p>
<img src=x onerror=eval("document.getElementById('test').innerHTML=window.location") />
`;
doc.html(html, {
  callback: function (doc) {
    doc.save();
  }
});

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade jspdf to version 2.0.0 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

lodash is a modern 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);

Details

Prototype Pollution is a vulnerability affecting JavaScript. Prototype Pollution refers to the ability to inject properties into existing JavaScript language construct prototypes, such as objects. JavaScript allows all Object attributes to be altered, including their magical attributes such as __proto__, constructor and prototype. An attacker manipulates these attributes to overwrite, or pollute, a JavaScript application object prototype of the base object by injecting other values. Properties on the Object.prototype are then inherited by all the JavaScript objects through the prototype chain. When that happens, this leads to either denial of service by triggering JavaScript exceptions, or it tampers with the application source code to force the code path that the attacker injects, thereby leading to remote code execution.

There are two main ways in which the pollution of prototypes occurs:

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

The logic of a vulnerable recursive merge function follows the following high-level model:

merge (target, source)

  foreach property of source

    if property exists and is an object on both the target and the source

      merge(target[property], source[property])

    else

      target[property] = source[property]

When the source object contains a property named __proto__ defined with Object.defineProperty() , the condition that checks if the property exists and is an object on both the target and the source passes and the merge recurses with the target, being the prototype of Object and the source of Object as defined by the attacker. Properties are then copied on the Object prototype.

Clone operations are a special sub-class of unsafe recursive merges, which occur when a recursive merge is conducted on an empty object: merge({},source).

lodash and Hoek are examples of libraries susceptible to recursive merge attacks.

Property definition by path

There are a few JavaScript libraries that use an API to define property values on an object based on a given path. The function that is generally affected contains this signature: theFunction(object, path, value)

If the attacker can control the value of “path”, they can set this value to __proto__.myValue. myValue is then assigned to the prototype of the class of the object.

Types of attacks

There are a few methods by which Prototype Pollution can be manipulated:

Type Origin Short description
Denial of service (DoS) Client This is the most likely attack.
DoS occurs when Object holds generic functions that are implicitly called for various operations (for example, toString and valueOf).
The attacker pollutes Object.prototype.someattr and alters its state to an unexpected value such as Int or Object. In this case, the code fails and is likely to cause a denial of service.
For example: if an attacker pollutes Object.prototype.toString by defining it as an integer, if the codebase at any point was reliant on someobject.toString() it would fail.
Remote Code Execution Client Remote code execution is generally only possible in cases where the codebase evaluates a specific attribute of an object, and then executes that evaluation.
For example: eval(someobject.someattr). In this case, if the attacker pollutes Object.prototype.someattr they are likely to be able to leverage this in order to execute code.
Property Injection Client The attacker pollutes properties that the codebase relies on for their informative value, including security properties such as cookies or tokens.
For example: if a codebase checks privileges for someuser.isAdmin, then when the attacker pollutes Object.prototype.isAdmin and sets it to equal true, they can then achieve admin privileges.

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

  5. As a best practice use Map instead of Object.

For more information on this vulnerability type:

Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018

Remediation

Upgrade lodash to version 4.17.5 or higher.

References

Prototype Pollution vulnerability report

medium severity

Server-side Request Forgery (SSRF)

  • Vulnerable module: axios
  • Introduced through: browser-sync@2.29.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › browser-sync@2.29.3 › localtunnel@2.0.2 › axios@0.21.4

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to the allowAbsoluteUrls attribute being ignored in the call to the buildFullPath function from the HTTP adapter. An attacker could launch SSRF attacks or exfiltrate sensitive data by tricking applications into sending requests to malicious endpoints.

PoC

const axios = require('axios');
const client = axios.create({baseURL: 'http://example.com/', allowAbsoluteUrls: false});
client.get('http://evil.com');

Remediation

Upgrade axios to version 0.30.0, 1.8.2 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity

Server-side Request Forgery (SSRF)

  • Vulnerable module: axios
  • Introduced through: browser-sync@2.29.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › browser-sync@2.29.3 › localtunnel@2.0.2 › axios@0.21.4

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) due to not setting allowAbsoluteUrls to false by default when processing a requested URL in buildFullPath(). It may not be obvious that this value is being used with the less safe default, and URLs that are expected to be blocked may be accepted. This is a bypass of the fix for the vulnerability described in CVE-2025-27152.

Remediation

Upgrade axios to version 0.30.0, 1.8.3 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: node-sass@4.14.1, gulp-sass@3.2.1 and others

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › sass-graph@2.2.5 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › true-case-path@1.0.3 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-stream@3.1.18 › glob@4.5.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin@5.3.1 › globby@6.1.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › sass-graph@2.2.5 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › true-case-path@1.0.3 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › gaze@1.1.3 › globule@1.3.4 › glob@7.1.7 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › exec-buffer@3.2.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › exec-buffer@3.2.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › exec-buffer@3.2.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › gaze@1.1.3 › globule@1.3.4 › glob@7.1.7 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob@5.0.15 › inflight@1.0.6

…and 42 more

Overview

Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime via the makeres function due to improperly deleting keys from the reqs object after execution of callbacks. This behavior causes the keys to remain in the reqs object, which leads to resource exhaustion.

Exploiting this vulnerability results in crashing the node process or in the application crash.

Note: This library is not maintained, and currently, there is no fix for this issue. To overcome this vulnerability, several dependent packages have eliminated the use of this library.

To trigger the memory leak, an attacker would need to have the ability to execute or influence the asynchronous operations that use the inflight module within the application. This typically requires access to the internal workings of the server or application, which is not commonly exposed to remote users. Therefore, “Attack vector” is marked as “Local”.

PoC

const inflight = require('inflight');

function testInflight() {
  let i = 0;
  function scheduleNext() {
    let key = `key-${i++}`;
    const callback = () => {
    };
    for (let j = 0; j < 1000000; j++) {
      inflight(key, callback);
    }

    setImmediate(scheduleNext);
  }


  if (i % 100 === 0) {
    console.log(process.memoryUsage());
  }

  scheduleNext();
}

testInflight();

Remediation

There is no fixed version for inflight.

References

Missing Release of Resource after Effective Lifetime vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: bootstrap
  • Introduced through: bootstrap@4.6.2

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › bootstrap@4.6.2
    Remediation: Upgrade to bootstrap@5.0.0.

Overview

bootstrap is a popular front-end framework for faster and easier web development.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the carousel component through the href attribute of an <a> tag due to inadequate sanitization. An attacker can execute arbitrary JavaScript within the victim's browser by crafting malicious input in the data-slide attribute.

Notes:

  1. Exploiting this vulnerability is also possible when the data_target attribute doesn’t exist or can’t be found, allowing the bypass of the clickHandler functionality.

PoC

<div id="myCarousel" class="carousel"></div>
<a href="javascript:alert('XSS href')" data-slide="prev">
  Previous Slide
</a>

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade bootstrap to version 5.0.0-beta1 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: bootstrap
  • Introduced through: bootstrap@4.6.2

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › bootstrap@4.6.2
    Remediation: Upgrade to bootstrap@5.0.0.

Overview

bootstrap is a popular front-end framework for faster and easier web development.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to inadequate sanitization of the href attribute, belonging to an <a> tag, in the carousel component. An attacker can execute arbitrary JavaScript within the victim's browser by injecting malicious code into the data-slide or data-slide-to attributes.

Notes:

  1. Exploiting this vulnerability is also possible when the data_target attribute doesn’t exist or can’t be found, allowing the bypass of the clickHandler functionality.

PoC

<div id="myCarousel" class="carousel"></div>
<a href="javascript:alert('XSS href')" data-slide="prev">
  Previous Slide
</a>

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade bootstrap to version 5.0.0-beta1 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: jspdf
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3
    Remediation: Upgrade to jspdf@2.3.1.

Overview

jspdf is a PDF Document creation from JavaScript

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). ReDoS is possible via the addImage function.

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 jspdf to version 2.3.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Open Redirect

  • Vulnerable module: got
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › got@5.7.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › got@5.7.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › got@5.7.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › got@5.7.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › got@5.7.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › got@5.7.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › got@5.7.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › got@5.7.1

…and 5 more

Overview

Affected versions of this package are vulnerable to Open Redirect due to missing verification of requested URLs. It allowed a victim to be redirected to a UNIX socket.

Remediation

Upgrade got to version 11.8.5, 12.1.0 or higher.

References

Open Redirect vulnerability report

medium severity

XML External Entity (XXE) Injection

  • Vulnerable module: xmldom
  • Introduced through: jspdf@1.5.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jspdf@1.5.3 › canvg@1.5.3 › xmldom@0.1.31
    Remediation: Upgrade to jspdf@2.5.2.

Overview

xmldom is an A pure JavaScript W3C standard-based (XML DOM Level 2 Core) DOMParser and XMLSerializer module.

Affected versions of this package are vulnerable to XML External Entity (XXE) Injection. Does not correctly preserve system identifiers, FPIs or namespaces when repeatedly parsing and serializing maliciously crafted documents.

Details

XXE Injection is a type of attack against an application that parses XML input. XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.

Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.

For example, below is a sample XML document, containing an XML element- username.

<xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
   <username>John</username>
</xml>

An external XML entity - xxe, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of /etc/passwd and display it to the user rendered by username.

<xml>
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE foo [
   <!ENTITY xxe SYSTEM "file:///etc/passwd" >]>
   <username>&xxe;</username>
</xml>

Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.

Remediation

Upgrade xmldom to version 0.5.0 or higher.

References

XML External Entity (XXE) Injection vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: axios
  • Introduced through: browser-sync@2.29.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › browser-sync@2.29.3 › localtunnel@2.0.2 › axios@0.21.4

Overview

axios is a promise-based HTTP client for the browser and Node.js.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). An attacker can deplete system resources by providing a manipulated string as input to the format method, causing the regular expression to exhibit a time complexity of O(n^2). This makes the server to become unable to provide normal service due to the excessive cost and time wasted in processing vulnerable regular expressions.

PoC

const axios = require('axios');

console.time('t1');
axios.defaults.baseURL = '/'.repeat(10000) + 'a/';
axios.get('/a').then(()=>{}).catch(()=>{});
console.timeEnd('t1');

console.time('t2');
axios.defaults.baseURL = '/'.repeat(100000) + 'a/';
axios.get('/a').then(()=>{}).catch(()=>{});
console.timeEnd('t2');


/* stdout
t1: 60.826ms
t2: 5.826s
*/

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 axios to version 0.29.0, 1.6.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: glob-parent
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › glob-parent@3.1.0

…and 17 more

Overview

glob-parent is a package that helps extracting the non-magic parent path from a glob string.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). The enclosure regex used to check for strings ending in enclosure containing path separator.

PoC by Yeting Li

var globParent = require("glob-parent")
function build_attack(n) {
var ret = "{"
for (var i = 0; i < n; i++) {
ret += "/"
}

return ret;
}

globParent(build_attack(5000));

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 glob-parent to version 5.1.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: is-svg
  • Introduced through: gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-svgo@6.0.0 › is-svg@2.1.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.

Overview

is-svg is a Check if a string or buffer is SVG

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, is-svg will get stuck processing the input for a very long time.

You are only affected if you use this package on a server that accepts SVG as user-input.

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 is-svg to version 4.2.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: is-svg
  • Introduced through: gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-svgo@6.0.0 › is-svg@2.1.0
    Remediation: Upgrade to gulp-imagemin@5.0.0.

Overview

is-svg is a Check if a string or buffer is SVG

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the removeDtdMarkupDeclarations and entityRegex regular expressions, bypassing the fix for CVE-2021-28092.

PoC by Yeting Li

//1) 1st ReDoS caused by the two sub-regexes [A-Z]+ and [^>]* in `removeDtdMarkupDeclarations`.
const isSvg = require('is-svg');
function build_attack1(n) {
var ret = '<!'
for (var i = 0; i < n; i++) {
ret += 'DOCTYPE'
}

return ret+"";
}
for(var i = 1; i <= 50000; i++) {
   if (i % 10000 == 0) {
       var time = Date.now();
       var attack_str = build_attack1(i);
       isSvg(attack_str);

       var time_cost = Date.now() - time;
       console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
 }
}

//2) 2nd ReDoS caused by ? the first sub-regex  \s*  in `entityRegex`.
function build_attack2(n) {
var ret = ''
for (var i = 0; i < n; i++) {
ret += ' '
}

return ret+"";
}
for(var i = 1; i <= 50000; i++) {
   if (i % 10000 == 0) {
       var time = Date.now();
       var attack_str = build_attack2(i);
       isSvg(attack_str);

       var time_cost = Date.now() - time;
       console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
 }
}


//3rd ReDoS caused by the sub-regex \s+\S*\s*  in `entityRegex`.
function build_attack3(n) {
var ret = '<!Entity'
for (var i = 0; i < n; i++) {
ret += ' '
}

return ret+"";
}
for(var i = 1; i <= 50000; i++) {
   if (i % 10000 == 0) {
       var time = Date.now();
       var attack_str = build_attack3(i);
       isSvg(attack_str);

       var time_cost = Date.now() - time;
       console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
 }
}

//4th ReDoS caused by the sub-regex \S*\s*(?:"|')[^"]+  in `entityRegex`.
function build_attack4(n) {
var ret = '<!Entity '
for (var i = 0; i < n; i++) {
ret += '\''
}

return ret+"";
}
for(var i = 1; i <= 50000; i++) {
   if (i % 10000 == 0) {
       var time = Date.now();
       var attack_str = build_attack4(i);
       isSvg(attack_str);

       var time_cost = Date.now() - time;
       console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms")
 }
}

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 is-svg to version 4.3.0 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

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

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions.

POC

var lo = require('lodash');

function build_blank (n) {
var ret = "1"
for (var i = 0; i < n; i++) {
ret += " "
}

return ret + "1";
}

var s = build_blank(50000)
var time0 = Date.now();
lo.trim(s)
var time_cost0 = Date.now() - time0;
console.log("time_cost0: " + time_cost0)

var time1 = Date.now();
lo.toNumber(s)
var time_cost1 = Date.now() - time1;
console.log("time_cost1: " + time_cost1)

var time2 = Date.now();
lo.trimEnd(s)
var time_cost2 = Date.now() - time2;
console.log("time_cost2: " + time_cost2)

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 lodash to version 4.17.21 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: minimatch
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-stream@3.1.18 › minimatch@2.0.10
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-stream@3.1.18 › glob@4.5.3 › minimatch@2.0.10
    Remediation: Upgrade to gulp@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › minimatch@0.2.14
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › 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

…and 1 more

Overview

minimatch is a minimal matching utility.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the braceExpand function in minimatch.js.

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 minimatch to version 3.0.5 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
    Remediation: Upgrade to node-sass@7.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Improper Certificate Validation. Certificate validation is disabled by default when requesting binaries, even if the user is not specifying an alternative download path.

Remediation

Upgrade node-sass to version 7.0.0 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: scss-tokenizer
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › sass-graph@2.2.5 › scss-tokenizer@0.2.3
    Remediation: Upgrade to node-sass@7.0.2.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › sass-graph@2.2.5 › scss-tokenizer@0.2.3
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the loadAnnotation() function, due to the usage of insecure regex.

PoC

var scss = require("scss-tokenizer")
function build_attack(n) {
    var ret = "a{}"
    for (var i = 0; i < n; i++) {
        ret += "/*# sourceMappingURL="
    }
    return ret + "!";
}

// postcss.parse('a{}/*# sourceMappingURL=a.css.map */')
for(var i = 1; i <= 500000; i++) {
    if (i % 1000 == 0) {
        var time = Date.now();
        var attack_str = build_attack(i)
        try{
            scss.tokenize(attack_str)
            var time_cost = Date.now() - time;
            console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms");
            }
        catch(e){
        var time_cost = Date.now() - time;
        console.log("attack_str.length: " + attack_str.length + ": " + time_cost+" ms");
        }
    }
}

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 scss-tokenizer to version 0.4.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: semver-regex
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0

…and 1 more

Overview

semver-regex is a Regular expression for matching semver versions

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to improper usage of regex in the semverRegex() function.

PoC

'0.0.1-' + '-.--'.repeat(i) + ' '

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 semver-regex to version 3.1.4, 4.0.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Uninitialized Memory Exposure

  • Vulnerable module: tunnel-agent
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to jpegtran-bin@4.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to gulp-imagemin@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › caw@1.2.0 › tunnel-agent@0.4.3
    Remediation: Upgrade to gulp-imagemin@5.0.0.

…and 5 more

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. Note This is vulnerable only for Node <=4

References

Uninitialized Memory Exposure vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: lodash
  • Introduced through: gulp@3.9.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp@3.9.1 › vinyl-fs@0.3.14 › glob-watcher@0.0.6 › gaze@0.5.2 › globule@0.1.0 › lodash@1.0.2

Overview

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

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 2 seconds per 50k characters.

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 lodash to version 4.17.11 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to NULL Pointer Dereference via Sass::Parser::parseCompoundSelectorin parser_selectors.cpp. Note: node-sass is affected by this vulnerability due to its bundled usage of the libsass package.

Remediation

There is no fixed version for node-sass.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Out-of-bounds Read via Sass::weaveParents in ast_sel_weave.cpp. Note: node-sass is affected by this vulnerability due to its bundled usage of the libsass package.

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

There is no fixed version for node-sass.

References

Out-of-bounds Read vulnerability report

medium severity

Uncontrolled Recursion

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1

Overview

node-sass is a Node.js bindings package for libsass.

Affected versions of this package are vulnerable to Uncontrolled Recursion via Sass::Eval::operator()(Sass::Binary_Expression*) in eval.cpp. Note: node-sass is affected by this vulnerability due to its bundled usage of the libsass package.

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

There is no fixed version for node-sass.

References

Uncontrolled Recursion vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: semver-regex
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › bin-version-check@2.1.0 › bin-version@1.0.4 › find-versions@1.2.1 › semver-regex@1.0.0

…and 1 more

Overview

semver-regex is a Regular expression for matching semver versions

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS).

PoC


// import of the vulnerable library
const semverRegex = require('semver-regex');
// import of measurement tools
const { PerformanceObserver, performance } = require('perf_hooks');

// config of measurements tools
const obs = new PerformanceObserver((items) => {
 console.log(items.getEntries()[0].duration);
 performance.clearMarks();
});
obs.observe({ entryTypes: ['measure'] });

// base version string
let version = "v1.1.3-0a"

// Adding the evil code, resulting in string
// v1.1.3-0aa.aa.aa.aa.aa.aa.a…a.a"
for(let i=0; i < 20; i++) {
   version += "a.a"
}

// produce a good version
// Parses well for the regex in milliseconds
let goodVersion = version + "2"

// good version proof
performance.mark("good before")
const goodresult = semverRegex().test(goodVersion);
performance.mark("good after")


console.log(`Good result: ${goodresult}`)
performance.measure('Good', 'good before', 'good after');

// create a bad/exploit version that is invalid due to the last $ sign
// will cause the nodejs engine to hang, if not, increase the a.a
// additions above a bit.
badVersion = version + "aaaaaaa$"

// exploit proof
performance.mark("bad before")
const badresult = semverRegex().test(badVersion);
performance.mark("bad after")

console.log(`Bad result: ${badresult}`)
performance.measure('Bad', 'bad before', 'bad after');

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 semver-regex to version 3.1.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

MPL-2.0 license

  • Module: mdn-data
  • Introduced through: gulp-csso@3.0.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-csso@3.0.1 › csso@3.5.1 › css-tree@1.0.0-alpha.29 › mdn-data@1.1.4

MPL-2.0 license

MPL-2.0 license vulnerability report

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: braces
  • Introduced through: jpegtran-bin@3.2.0 and gulp-imagemin@4.1.0

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-build@2.2.0 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-gifsicle@5.2.0 › gifsicle@3.0.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-jpegtran@5.0.2 › jpegtran-bin@3.2.0 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-imagemin@4.1.0 › imagemin-optipng@5.2.1 › optipng-bin@3.1.4 › bin-wrapper@3.0.2 › download@4.4.3 › gulp-decompress@1.2.0 › decompress@3.0.0 › vinyl-fs@2.4.4 › glob-stream@5.3.5 › micromatch@2.3.11 › braces@1.8.5

…and 17 more

Overview

braces is a Bash-like brace expansion, implemented in JavaScript.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). It used a regular expression (^\{(,+(?:(\{,+\})*),*|,*(?:(\{,+\})*),+)\}) in order to detects empty braces. This can cause an impact of about 10 seconds matching time for data 50K 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 19th, 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 braces to version 2.3.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: tar
  • Introduced through: node-sass@4.14.1 and gulp-sass@3.2.1

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › gulp-sass@3.2.1 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to gulp-sass@5.0.0.

Overview

tar is a full-featured Tar for Node.js.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). When stripping the trailing slash from files arguments, the f.replace(/\/+$/, '') performance of this function can exponentially degrade when f contains many / characters resulting in ReDoS.

This vulnerability is not likely to be exploitable as it requires that the untrusted input is being passed into the tar.extract() or tar.list() array of entries to parse/extract, which would be unusual.

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 tar to version 6.1.4, 5.0.8, 4.4.16 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

low severity

Cross-site Scripting

  • Vulnerable module: send
  • Introduced through: browser-sync@2.29.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › browser-sync@2.29.3 › send@0.16.2
    Remediation: Upgrade to browser-sync@3.0.3.
  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › browser-sync@2.29.3 › serve-static@1.13.2 › send@0.16.2
    Remediation: Upgrade to browser-sync@3.0.3.

Overview

send is a Better streaming static file server with Range and conditional-GET support

Affected versions of this package are vulnerable to Cross-site Scripting due to improper user input sanitization passed to the SendStream.redirect() function, which executes untrusted code. An attacker can execute arbitrary code by manipulating the input parameters to this method.

Note:

Exploiting this vulnerability requires the following:

  1. The attacker needs to control the input to response.redirect()

  2. Express MUST NOT redirect before the template appears

  3. The browser MUST NOT complete redirection before

  4. The user MUST click on the link in the template

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade send to version 0.19.0, 1.1.0 or higher.

References

Cross-site Scripting vulnerability report

low severity

Cross-site Scripting

  • Vulnerable module: serve-static
  • Introduced through: browser-sync@2.29.3

Detailed paths

  • Introduced through: resume@sonyccd/resume#f01c3b42a40745a4c8e02b7cd108ff88ae27ecc7 › browser-sync@2.29.3 › serve-static@1.13.2
    Remediation: Upgrade to browser-sync@3.0.3.

Overview

serve-static is a server.

Affected versions of this package are vulnerable to Cross-site Scripting due to improper sanitization of user input in the redirect function. An attacker can manipulate the redirection process by injecting malicious code into the input.

Note

To exploit this vulnerability, the following conditions are required:

  1. The attacker should be able to control the input to response.redirect()

  2. express must not redirect before the template appears

  3. the browser must not complete redirection before:

  4. the user must click on the link in the template

Details

A cross-site scripting attack occurs when the attacker tricks a legitimate web-based application or site to accept a request as originating from a trusted source.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, < can be coded as &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

Types of attacks

There are a few methods by which XSS can be manipulated:

Type Origin Description
Stored Server The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected Server The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based Client The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

This section describes the top best practices designed to specifically protect your code:

  • Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
  • Convert special characters such as ?, &, /, <, > and spaces to their respective HTML or URL encoded equivalents.
  • Give users the option to disable client-side scripts.
  • Redirect invalid requests.
  • Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
  • Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
  • Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

Remediation

Upgrade serve-static to version 1.16.0, 2.1.0 or higher.

References

Cross-site Scripting vulnerability report