react-15.7.0.tgz: 3 vulnerabilities (highest severity is: 7.5)

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

Vulnerable Library - react-15.7.0.tgz

Path to dependency file: /sdk-wrapper-react-sample/package.json

Path to vulnerable library: /sdk-wrapper-react-sample/node_modules/ua-parser-js/package.json

Vulnerabilities

CVE	Severity	CVSS	Dependency	Type	Fixed in (react version)	Remediation Available
CVE-2022-25927	High	7.5	ua-parser-js-0.7.31.tgz	Transitive	16.0.0	✅
CVE-2022-0235	Medium	6.1	node-fetch-1.7.3.tgz	Transitive	16.5.0	✅
CVE-2020-15168	Medium	5.3	node-fetch-1.7.3.tgz	Transitive	16.5.0	✅

Details

CVE-2022-25927

Vulnerable Library - ua-parser-js-0.7.31.tgz

Detect Browser, Engine, OS, CPU, and Device type/model from User-Agent data. Supports browser & node.js environment

Library home page: https://registry.npmjs.org/ua-parser-js/-/ua-parser-js-0.7.31.tgz

Path to dependency file: /sdk-wrapper-react-sample/package.json

Path to vulnerable library: /sdk-wrapper-react-sample/node_modules/ua-parser-js/package.json

Dependency Hierarchy:

• react-15.7.0.tgz (Root Library)
  • fbjs-0.8.18.tgz
    • :x: ua-parser-js-0.7.31.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

Versions of the package ua-parser-js from 0.7.30 and before 0.7.33, from 0.8.1 and before 1.0.33 are vulnerable to Regular Expression Denial of Service (ReDoS) via the trim() function.

Publish Date: 2022-02-24

URL: CVE-2022-25927

CVSS 3 Score Details (7.5)

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2022-02-24

Fix Resolution (ua-parser-js): 1.0.33

Direct dependency fix Resolution (react): 16.0.0

:rescue_worker_helmet: Automatic Remediation is available for this issue

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: /sdk-wrapper-react-sample/package.json

Path to vulnerable library: /sdk-wrapper-react-sample/node_modules/node-fetch/package.json

Dependency Hierarchy:

• react-15.7.0.tgz (Root Library)
  • fbjs-0.8.18.tgz
    • isomorphic-fetch-2.2.1.tgz
      • :x: node-fetch-1.7.3.tgz (Vulnerable Library)

Found in base branch: main

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

Direct dependency fix Resolution (react): 16.5.0

:rescue_worker_helmet: Automatic Remediation is available for this issue

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: /sdk-wrapper-react-sample/package.json

Path to vulnerable library: /sdk-wrapper-react-sample/node_modules/node-fetch/package.json

Dependency Hierarchy:

• react-15.7.0.tgz (Root Library)
  • fbjs-0.8.18.tgz
    • isomorphic-fetch-2.2.1.tgz
      • :x: node-fetch-1.7.3.tgz (Vulnerable Library)

Found in base branch: main

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 (node-fetch): 2.6.1

Direct dependency fix Resolution (react): 16.5.0

:rescue_worker_helmet: Automatic Remediation is available for this issue

---

:rescue_worker_helmet: Automatic Remediation is available for this issue.