CVE-2020-15168 (Low) detected in multiple libraries

[mend-bolt-for-github[bot]]

CVE-2020-15168 - Low Severity Vulnerability

Vulnerable Libraries - node-fetch-1.7.3.tgz, node-fetch-2.2.1.tgz, node-fetch-2.6.0.tgz

node-fetch-1.7.3.tgz

A light-weight module that brings window.fetch to node.js and io.js

Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-1.7.3.tgz

Path to dependency file: /aws-node-fetch-file-and-store-in-s3/package.json

Path to vulnerable library: /aws-node-fetch-file-and-store-in-s3/node_modules/node-fetch/package.json,/aws-node-oauth-dropbox-api/node_modules/node-fetch/package.json,/aws-dotnet-rest-api-with-dynamodb/src/DotNetServerless.Lambda/node_modules/node-fetch/package.json,/aws-node-typescript-apollo-lambda/node_modules/isomorphic-fetch/node_modules/node-fetch/package.json,/aws-node-signed-uploads/node_modules/node-fetch/package.json

Dependency Hierarchy: - :x: **node-fetch-1.7.3.tgz** (Vulnerable Library)

node-fetch-2.2.1.tgz

A light-weight module that brings window.fetch to node.js

Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-2.2.1.tgz

Path to dependency file: /aws-node-twitter-joke-bot/package.json

Path to vulnerable library: /aws-node-twitter-joke-bot/node_modules/node-fetch/package.json

Dependency Hierarchy: - :x: **node-fetch-2.2.1.tgz** (Vulnerable Library)

node-fetch-2.6.0.tgz

A light-weight module that brings window.fetch to node.js

Library home page: https://registry.npmjs.org/node-fetch/-/node-fetch-2.6.0.tgz

Path to dependency file: /aws-node-typescript-apollo-lambda/package.json

Path to vulnerable library: /aws-node-typescript-apollo-lambda/node_modules/node-fetch/package.json

Dependency Hierarchy: - serverless-1.79.0.tgz (Root Library) - :x: **node-fetch-2.6.0.tgz** (Vulnerable Library)

Found in HEAD commit: dcbe4aefe4b3685f4b15493a01db0f19b118a0c4

Found in base branch: master

Vulnerability Details

node-fetch before versions 2.6.1 and 3.0.0-beta.9 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. For most people, this fix will have a little or no impact. However, if you are relying on node-fetch to gate files above a size, the impact could be significant, for example: If you don't double-check the size of the data after fetch() has completed, your JS thread could get tied up doing work on a large file (DoS) and/or cost you money in computing.

Publish Date: 2020-09-10

URL: CVE-2020-15168

CVSS 3 Score Details (2.6)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: Required - 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

Origin: https://github.com/node-fetch/node-fetch/security/advisories/GHSA-w7rc-rwvf-8q5r

Release Date: 2020-09-17

Fix Resolution (node-fetch): 2.6.1

Direct dependency fix Resolution (serverless): 1.80.0-06ed01b8

---

Step up your Open Source Security Game with Mend here

[mend-bolt-for-github[bot]]

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

[mend-bolt-for-github[bot]]

:information_source: This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.