Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Upgrade node-fetch from 2.6.0 to 3.3.2 #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Upgrade node-fetch from 2.6.0 to 3.3.2 #3

wants to merge 1 commit into from

Conversation

naiba4
Copy link
Owner

@naiba4 naiba4 commented Aug 31, 2023

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade node-fetch from 2.6.0 to 3.3.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 42 versions ahead of your current version.
  • The recommended version was released a month ago, on 2023-07-25.

The recommended version fixes:

Severity Issue PriorityScore (*) Exploit Maturity
Information Exposure
SNYK-JS-NODEFETCH-2342118		 138/1000
Why? Confidentiality impact: High, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): Low, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.0011, Social Trends: No, Days since published: 591, Transitive dependency: No, Is Malicious: No, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.3, Score Version: V4		 No Known Exploit
Denial of Service
SNYK-JS-NODEFETCH-674311		 138/1000
Why? Confidentiality impact: High, Integrity impact: None, Availability impact: None, Scope: Unchanged, Exploit Maturity: No data, User Interaction (UI): None, Privileges Required (PR): Low, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.0011, Social Trends: No, Days since published: 591, Transitive dependency: No, Is Malicious: No, Provider Urgency: Medium, Package Popularity Score: 99, Impact: 5.99, Likelihood: 2.3, Score Version: V4		 No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes
Package name: node-fetch
  • 3.3.2 - 2023-07-25

    3.3.2 (2023-07-25)

    Bug Fixes

  • 3.3.1 - 2023-03-11

    3.3.1 (2023-03-11)

    Bug Fixes

    • release "Allow URL class object as an argument for fetch()" #1696 (#1716) (7b86e94)
  • 3.3.0 - 2022-11-10

    3.3.0 (2022-11-10)

    Features

  • 3.2.10 - 2022-07-31

    3.2.10 (2022-07-31)

    Bug Fixes

  • 3.2.9 - 2022-07-18

    3.2.9 (2022-07-18)

    Bug Fixes

    • Headers: don't forward secure headers on protocol change (#1599) (e87b093)
  • 3.2.8 - 2022-07-12
  • 3.2.7 - 2022-07-11
  • 3.2.6 - 2022-06-09
  • 3.2.5 - 2022-06-01
  • 3.2.4 - 2022-04-28
  • 3.2.3 - 2022-03-11
  • 3.2.2 - 2022-03-07
  • 3.2.1 - 2022-03-01
  • 3.2.0 - 2022-01-20
  • 3.1.1 - 2022-01-16
  • 3.1.0 - 2021-11-08
  • 3.0.0 - 2021-08-31
  • 3.0.0-beta.6-exportfix - 2020-05-25
  • 3.0.0-beta.10 - 2021-07-19
  • 3.0.0-beta.9 - 2020-09-05
  • 3.0.0-beta.8 - 2020-08-10
  • 3.0.0-beta.7 - 2020-06-11
  • 3.0.0-beta.6 - 2020-05-25
  • 3.0.0-beta.5 - 2020-04-22
  • 3.0.0-beta.4 - 2020-03-14
  • 3.0.0-beta.3 - 2020-03-13
  • 3.0.0-beta.2 - 2020-03-13
  • 3.0.0-beta.1 - 2020-03-13
  • 2.7.0 - 2023-08-23
  • 2.6.13 - 2023-08-18
  • 2.6.12 - 2023-06-29

    2.6.12 (2023-06-29)

    Bug Fixes

  • 2.6.11 - 2023-05-09

    2.6.11 (2023-05-09)

    Reverts

  • 2.6.10 - 2023-05-08

    2.6.10 (2023-05-08)

    Bug Fixes

  • 2.6.9 - 2023-01-30

    2.6.9 (2023-01-30)

    Bug Fixes

  • 2.6.8 - 2023-01-13

    2.6.8 (2023-01-13)

    Bug Fixes

  • 2.6.7 - 2022-01-16
  • 2.6.6 - 2021-10-31
  • 2.6.5 - 2021-09-22
  • 2.6.4 - 2021-09-21
  • 2.6.3 - 2021-09-20
  • 2.6.2 - 2021-09-06
  • 2.6.1 - 2020-09-05
  • 2.6.0 - 2019-05-16
from node-fetch GitHub release notes
Commit messages
Package name: node-fetch

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@socket-security
Copy link

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Packages Version New capabilities Transitives Size Publisher
node-fetch 2.6.0...3.3.2 None +5/-0 7.81 MB node-fetch-bot

@socket-security
Copy link

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue Package Version Note Source
Chronological version anomaly node-fetch 3.3.2
URL strings node-fetch 3.3.2
Major refactor data-uri-to-buffer 4.0.1
  • Change Percentage: 50.86
  • Current Line Count: 125
  • Previous Line Count: 339
  • Lines Changed: 236
Unmaintained web-streams-polyfill 3.2.1
  • Last Publish: 5/24/2022, 7:52:20 PM
Unmaintained formdata-polyfill 4.0.10
  • Last Publish: 9/30/2021, 1:07:58 PM

Next steps

What is a chronological version anomaly?

Semantic versions published out of chronological order.

This could either indicate dependency confusion or a patched vulnerability.

What are URL strings?

Package contains fragments of external URLs or IP addresses, which may indicate that it covertly exfiltrates data.

Avoid using packages that make connections to the network, since this helps to leak data.

What is a major refactor?

Package has recently undergone a major refactor. It may be unstable or indicate significant internal changes. Use caution when updating to versions that include significant changes.

Consider waiting before upgrading to see if any issues are discovered, or be prepared to scrutinize any bugs or subtle changes the major refactor may bring. Publishers my consider publishing beta versions of major refactors to limit disruption to parties interested in the new changes.

What are unmaintained packages?

Package has not been updated in more than a year and may be unmaintained. Problems with the package may go unaddressed.

Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] bar@* or ignore all packages with @SocketSecurity ignore-all

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@naiba4 @snyk-bot