WS-2019-0425 (Medium) detected in multiple libraries - autoclosed

[mend-for-github-com]

WS-2019-0425 - Medium Severity Vulnerability

Vulnerable Libraries - mocha-2.2.5.js, mocha-1.21.5.tgz, mocha-1.8.1.js

mocha-2.2.5.js

simple, flexible, fun test framework

Library home page: https://cdnjs.cloudflare.com/ajax/libs/mocha/2.2.5/mocha.js

Path to dependency file: /npm_and_yarn/spec/fixtures/projects/yarn/duplicate_indirect_dependency/node_modules/js-base64/.attic/test-moment/index.html

Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/yarn/duplicate_indirect_dependency/node_modules/js-base64/.attic/test-moment/index.html

Dependency Hierarchy:

• ❌ mocha-2.2.5.js (Vulnerable Library)

mocha-1.21.5.tgz

simple, flexible, fun test framework

Library home page: https://registry.npmjs.org/mocha/-/mocha-1.21.5.tgz

Path to dependency file: /npm_and_yarn/spec/fixtures/projects/npm6/path_dependency/deps/etag/package.json

Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/npm6/path_dependency/deps/etag/node_modules/mocha/package.json,/npm_and_yarn/spec/fixtures/projects/npm7/path_dependency/deps/etag/node_modules/mocha/package.json,/npm_and_yarn/spec/fixtures/projects/npm7/library/node_modules/mocha/package.json,/npm_and_yarn/spec/fixtures/projects/npm6_and_yarn/path_dependency/deps/etag/node_modules/mocha/package.json,/npm_and_yarn/spec/fixtures/projects/npm6/etag_no_lockfile/node_modules/mocha/package.json

Dependency Hierarchy:

• ❌ mocha-1.21.5.tgz (Vulnerable Library)

mocha-1.8.1.js

simple, flexible, fun test framework

Library home page: https://cdnjs.cloudflare.com/ajax/libs/mocha/1.8.1/mocha.js

Path to dependency file: /npm_and_yarn/spec/fixtures/projects/npm6/git_dependency_local_file/node_modules/component-each/node_modules/component-type/test/index.html

Path to vulnerable library: /npm_and_yarn/spec/fixtures/projects/npm6/git_dependency_local_file/node_modules/component-each/node_modules/component-type/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/yarn/git_dependency_local_file/node_modules/component-type/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/npm6/git_dependency_local_file/node_modules/component-type/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/yarn/git_dependency_local_file/node_modules/to-no-case/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/npm7/git_dependency_local_file/node_modules/to-no-case/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/yarn/git_dependency_local_file/node_modules/component-each/node_modules/component-type/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/npm6/git_dependency_local_file/node_modules/to-no-case/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/npm7/git_dependency_local_file/node_modules/component-each/node_modules/component-type/test/mocha.js,/npm_and_yarn/spec/fixtures/projects/npm7/git_dependency_local_file/node_modules/component-type/test/mocha.js

Dependency Hierarchy:

• ❌ mocha-1.8.1.js (Vulnerable Library)

Found in HEAD commit: ba8cd9078c8ce0cb202767d627706711237abf71

Found in base branch: main

Vulnerability Details

Mocha is vulnerable to ReDoS attack. If the stack trace in utils.js begins with a large error message, and full-trace is not enabled, utils.stackTraceFilter() will take exponential run time.

Publish Date: 2019-01-24

URL: WS-2019-0425

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2019-01-24

Fix Resolution: v6.0.0

---

⛑️ Automatic Remediation will be attempted for this issue.

[mend-for-github-com]

✔️ This issue was automatically closed by WhiteSource because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the WhiteSource inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by WhiteSource because the vulnerable library in the specific branch(es) has been detected in the WhiteSource inventory.