WS-2019-0311 (Medium) detected in mongodb-2.2.36.tgz, mongodb-2.2.34.tgz

[mend-for-github-com]

WS-2019-0311 - Medium Severity Vulnerability

Vulnerable Libraries - mongodb-2.2.36.tgz, mongodb-2.2.34.tgz

mongodb-2.2.36.tgz

The official MongoDB driver for Node.js

Library home page: https://registry.npmjs.org/mongodb/-/mongodb-2.2.36.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/mongodb/package.json

Dependency Hierarchy:

• connect-mongo-2.0.3.tgz (Root Library)
  • ❌ mongodb-2.2.36.tgz (Vulnerable Library)

mongodb-2.2.34.tgz

The official MongoDB driver for Node.js

Library home page: https://registry.npmjs.org/mongodb/-/mongodb-2.2.34.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/mongoose/node_modules/mongodb/package.json

Dependency Hierarchy:

• mongoose-4.13.21.tgz (Root Library)
  • ❌ mongodb-2.2.34.tgz (Vulnerable Library)

Found in HEAD commit: 2e9d597fe70064b9c61d9203c8a93a380a667238

Found in base branch: master

Vulnerability Details

In 'node-mongodb-native', versions prior to v3.1.13 are vulnerable against DOS as a result of a potential crash when a collection name is invalid and the DB doesn't exist.

Publish Date: 2019-01-23

URL: WS-2019-0311

CVSS 3 Score Details (6.5)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.npmjs.com/advisories/1203

Release Date: 2019-01-23

Fix Resolution (mongodb): 3.1.13

Direct dependency fix Resolution (connect-mongo): 3.0.0

Fix Resolution (mongodb): 3.1.13

Direct dependency fix Resolution (mongoose): 5.4.10

---

⛑️ Automatic Remediation will be attempted for this issue.