react-native-calendars-1.1291.0.tgz: 2 vulnerabilities (highest severity is: 6.1) - autoclosed

[mend-for-github-com[bot]]

Vulnerable Library - react-native-calendars-1.1291.0.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/isomorphic-fetch/node_modules/node-fetch/package.json

Found in HEAD commit: 9af660e399b4f97f081ca047abb7e8fd6b0094f5

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (react-native-calendars version)	Remediation Available
CVE-2022-0235	Medium	6.1	node-fetch-1.7.3.tgz	Transitive	N/A*	❌
CVE-2020-15168	Medium	5.3	node-fetch-1.7.3.tgz	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.

Details

CVE-2022-0235

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

Path to vulnerable library: /node_modules/isomorphic-fetch/node_modules/node-fetch/package.json

Dependency Hierarchy: - react-native-calendars-1.1291.0.tgz (Root Library) - recyclerlistview-3.0.5.tgz - prop-types-15.5.8.tgz - fbjs-0.8.18.tgz - isomorphic-fetch-2.2.1.tgz - :x: **node-fetch-1.7.3.tgz** (Vulnerable Library)

Found in HEAD commit: 9af660e399b4f97f081ca047abb7e8fd6b0094f5

Found in base branch: master

### Vulnerability Details

node-fetch is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor

Publish Date: 2022-01-16

URL: CVE-2022-0235

### CVSS 3 Score Details (6.1)

Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-r683-j2x4-v87g

Release Date: 2022-01-16

Fix Resolution: node-fetch - 2.6.7,3.1.1

CVE-2020-15168

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

Path to vulnerable library: /node_modules/isomorphic-fetch/node_modules/node-fetch/package.json

Dependency Hierarchy: - react-native-calendars-1.1291.0.tgz (Root Library) - recyclerlistview-3.0.5.tgz - prop-types-15.5.8.tgz - fbjs-0.8.18.tgz - isomorphic-fetch-2.2.1.tgz - :x: **node-fetch-1.7.3.tgz** (Vulnerable Library)

Found in HEAD commit: 9af660e399b4f97f081ca047abb7e8fd6b0094f5

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 (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

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

Release Date: 2020-09-17

Fix Resolution: 2.6.1,3.0.0-beta.9

[mend-for-github-com[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.