mongodb-2.2.36.tgz: 2 vulnerabilities (highest severity is: 9.8) reachable

[mend-local-app]

Vulnerable Library - 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: /NodeGoat/package.json

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

Found in HEAD commit: 7301fa7a68e571bf3ddba7c1cd6704c9d04923a6

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (mongodb version)	Remediation Possible**	Reachability
CVE-2020-7610	High	9.8	bson-1.0.9.tgz	Transitive	3.1.3	✅
WS-2019-0311	Medium	6.5	mongodb-2.2.36.tgz	Direct	3.1.13	✅

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2020-7610

Vulnerable Library - bson-1.0.9.tgz

A bson parser for node.js and the browser

Library home page: https://registry.npmjs.org/bson/-/bson-1.0.9.tgz

Path to dependency file: /NodeGoat/package.json

Path to vulnerable library: /NodeGoat/node_modules/bson/package.json

Dependency Hierarchy:

• mongodb-2.2.36.tgz (Root Library)
  • mongodb-core-2.1.20.tgz
    • ❌ bson-1.0.9.tgz (Vulnerable Library)

Found in HEAD commit: 7301fa7a68e571bf3ddba7c1cd6704c9d04923a6

Found in base branch: main

Reachability Analysis

This vulnerability is potentially used

owasp-nodejs-goat-1.3.0/server.js (Application)
  -> mongodb-2.2.36/index.js (Extension)
   -> mongodb-core-2.1.20/index.js (Extension)
    -> bson-1.0.9/index.js (Extension)
     -> bson-1.0.9/lib/bson/bson.js (Extension)
      -> ❌ bson-1.0.9/lib/bson/parser/serializer.js (Vulnerable Component)

Vulnerability Details

All versions of bson before 1.1.4 are vulnerable to Deserialization of Untrusted Data. The package will ignore an unknown value for an object's _bsotype, leading to cases where an object is serialized as a document rather than the intended BSON type.

Publish Date: 2020-03-30

URL: CVE-2020-7610

CVSS 3 Score Details (9.8)

Base Score Metrics:

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2020-04-01

Fix Resolution (bson): 1.1.4

Direct dependency fix Resolution (mongodb): 3.1.3

In order to enable automatic remediation, please create workflow rules

WS-2019-0311

Vulnerable Library - 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: /NodeGoat/package.json

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

Dependency Hierarchy:

• ❌ mongodb-2.2.36.tgz (Vulnerable Library)

Found in HEAD commit: 7301fa7a68e571bf3ddba7c1cd6704c9d04923a6

Found in base branch: main

Reachability Analysis

This vulnerability is potentially used

owasp-nodejs-goat-1.3.0/server.js (Application)
  -> mongodb-2.2.36/index.js (Extension)
   -> ❌ mongodb-2.2.36/lib/collection.js (Vulnerable Component)

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: 3.1.13

In order to enable automatic remediation, please create workflow rules

---

In order to enable automatic remediation for this issue, please create workflow rules