Find, fix and prevent vulnerabilities in your code.
high severity
new
- Vulnerable module: react-router
- Introduced through: react-router-dom@4.3.1
Detailed paths
-
Introduced through: tgr-react-app@TGRstack/react-app#202cb825d461a54dff8e8a296009a01177ec16b3 › react-router-dom@4.3.1 › react-router@4.3.1Remediation: Upgrade to react-router-dom@6.30.2.
Overview
Affected versions of this package are vulnerable to Open Redirect via the resolvePath() function when used with navigate, <Link>, or redirect. An attacker can cause the application to redirect users to external, potentially malicious URLs by supplying crafted paths.
Note:
This is only exploitable if untrusted content is passed into navigation paths in the application code.
Remediation
Upgrade react-router to version 6.30.2, 7.9.6 or higher.
References
medium severity
- Vulnerable module: node-fetch
- Introduced through: react-apollo@2.1.11
Detailed paths
-
Introduced through: tgr-react-app@TGRstack/react-app#202cb825d461a54dff8e8a296009a01177ec16b3 › react-apollo@2.1.11 › fbjs@0.8.18 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-apollo@2.5.0.
Overview
node-fetch is a light-weight module that brings window.fetch to node.js
Affected versions of this package are vulnerable to Information Exposure when fetching a remote url with Cookie, if it get a Location response header, it will follow that url and try to fetch that url with provided cookie. This can lead to forwarding secure headers to 3th party.
Remediation
Upgrade node-fetch to version 2.6.7, 3.1.1 or higher.
References
medium severity
- Vulnerable module: node-fetch
- Introduced through: react-apollo@2.1.11
Detailed paths
-
Introduced through: tgr-react-app@TGRstack/react-app#202cb825d461a54dff8e8a296009a01177ec16b3 › react-apollo@2.1.11 › fbjs@0.8.18 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3Remediation: Upgrade to react-apollo@2.5.0.
Overview
node-fetch is a light-weight module that brings window.fetch to node.js
Affected versions of this package are vulnerable to Denial of Service (DoS). Node Fetch 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.
Remediation
Upgrade node-fetch to version 2.6.1, 3.0.0-beta.9 or higher.