Vulnerabilities

 2 via 4 paths

Dependencies

 62

Source

 npm
Find a vulnerability free version of @agungrizkyana/react-daterange-picker | View @agungrizkyana/react-daterange-picker package health on Snyk Advisor

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 2
Status
  • 2
  • 0
  • 0

medium severity
new

Information Exposure

  • Vulnerable module: node-fetch
  • Introduced through: @material-ui/core@3.9.4 and @material-ui/icons@3.0.2

Detailed paths

  • Introduced through: @agungrizkyana/react-daterange-picker@1.0.5 › @material-ui/core@3.9.4 › recompose@0.30.0 › fbjs@0.8.18 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3
  • Introduced through: @agungrizkyana/react-daterange-picker@1.0.5 › @material-ui/icons@3.0.2 › recompose@0.30.0 › fbjs@0.8.18 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3

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

Information Exposure vulnerability report

medium severity

Denial of Service

  • Vulnerable module: node-fetch
  • Introduced through: @material-ui/core@3.9.4 and @material-ui/icons@3.0.2

Detailed paths

  • Introduced through: @agungrizkyana/react-daterange-picker@1.0.5 › @material-ui/core@3.9.4 › recompose@0.30.0 › fbjs@0.8.18 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3
  • Introduced through: @agungrizkyana/react-daterange-picker@1.0.5 › @material-ui/icons@3.0.2 › recompose@0.30.0 › fbjs@0.8.18 › isomorphic-fetch@2.2.1 › node-fetch@1.7.3

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

References

Denial of Service vulnerability report