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.

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

[Snyk] Upgrade undici from 5.11.0 to 5.28.5 #144

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

Conversation

X-oss-byte
Copy link
Owner

@X-oss-byte X-oss-byte commented Feb 7, 2025

snyk-top-banner

Snyk has created this PR to upgrade undici from 5.11.0 to 5.28.5.

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


  • The recommended version is 47 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-UNDICI-3323845
551 Proof of Concept
high severity Insecure Randomness
SNYK-JS-UNDICI-8641354
551 Proof of Concept
medium severity CRLF Injection
SNYK-JS-UNDICI-3323844
551 Proof of Concept
low severity Information Exposure
SNYK-JS-UNDICI-5962466
551 No Known Exploit
low severity Permissive Cross-domain Policy with Untrusted Domains
SNYK-JS-UNDICI-6252336
551 No Known Exploit
low severity Improper Access Control
SNYK-JS-UNDICI-6564963
551 No Known Exploit
low severity Improper Authorization
SNYK-JS-UNDICI-6564964
551 No Known Exploit
Release notes
Package name: undici
  • 5.28.5 - 2025-01-16

    ⚠️ Security Release ⚠️

    Fixes CVE CVE-2025-22150 GHSA-c76h-2ccp-4975 (embargoed until 22-01-2025).

    Full Changelog: v5.28.4...v5.28.5

  • 5.28.4 - 2024-04-02
  • 5.28.3 - 2024-02-05
  • 5.28.2 - 2023-11-30
  • 5.28.1 - 2023-11-27
  • 5.28.0 - 2023-11-24
  • 5.27.2 - 2023-11-03
  • 5.27.1 - 2023-11-03
  • 5.27.0 - 2023-10-26
  • 5.26.5 - 2023-10-23
  • 5.26.4 - 2023-10-19
  • 5.26.3 - 2023-10-11
  • 5.26.2 - 2023-10-11
  • 5.26.1 - 2023-10-11
  • 5.26.0 - 2023-10-11
  • 5.25.4 - 2023-10-03
  • 5.25.3 - 2023-10-01
  • 5.25.2 - 2023-09-22
  • 5.25.1 - 2023-09-20
  • 5.25.0 - 2023-09-20
  • 5.24.0 - 2023-09-08
  • 5.24.0-test.6 - 2023-09-20
  • 5.24.0-test.5 - 2023-09-19
  • 5.24.0-test.4 - 2023-09-19
  • 5.24.0-test.3 - 2023-09-19
  • 5.24.0-test.2 - 2023-09-19
  • 5.24.0-test.1 - 2023-09-19
  • 5.24.0-test.0 - 2023-09-19
  • 5.23.0 - 2023-08-03
  • 5.22.1 - 2023-05-11
  • 5.22.0 - 2023-04-20
  • 5.21.2 - 2023-04-09
  • 5.21.1 - 2023-04-08
  • 5.21.0 - 2023-03-13
  • 5.20.0 - 2023-02-18
  • 5.19.1 - 2023-02-13
  • 5.19.0 - 2023-02-13
  • 5.18.0 - 2023-02-06
  • 5.17.1 - 2023-02-04
  • 5.17.0 - 2023-02-04
  • 5.16.0 - 2023-01-23
  • 5.15.2 - 2023-01-22
  • 5.15.1 - 2023-01-19
  • 5.15.0 - 2023-01-11
  • 5.14.0 - 2022-12-08
  • 5.13.0 - 2022-11-25
  • 5.12.0 - 2022-10-27
  • 5.11.0 - 2022-10-03
from undici GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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:

Summary by Sourcery

Upgrade undici from 5.11.0 to 5.28.5 to address multiple security vulnerabilities, including ReDoS and insecure randomness.

Bug Fixes:

  • Fix Regular Expression Denial of Service (ReDoS).
  • Fix insecure randomness.
  • Fix CRLF Injection.
  • Fix information exposure.
  • Fix permissive cross-domain policy with untrusted domains.
  • Fix improper access control.
  • Fix improper authorization.

Snyk has created this PR to upgrade undici from 5.11.0 to 5.28.5.

See this package in npm:
undici

See this project in Snyk:
https://app.snyk.io/org/sammytezzy/project/4719743d-c4ae-4210-8075-52671fe648e2?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

stackblitz bot commented Feb 7, 2025

Review PR in StackBlitz Codeflow Run & review this pull request in StackBlitz Codeflow.

Copy link

changeset-bot bot commented Feb 7, 2025

⚠️ No Changeset found

Latest commit: 912e154

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

sourcery-ai bot commented Feb 7, 2025

Reviewer's Guide by Sourcery

This pull request upgrades the undici dependency from version 5.11.0 to 5.28.5. The upgrade is implemented by modifying the package.json file in the apps/examples/solid-start directory, updating the version of undici to address several security vulnerabilities highlighted by Snyk.

Flow diagram for undici dependency upgrade and vulnerability fix

flowchart TD
    A[Snyk identifies security vulnerabilities in undici v5.11.0] --> B[Generate upgrade PR]
    B --> C[Update package.json in apps/examples/solid-start]
    C --> D[Change undici version from 5.11.0 to 5.28.5]
    D --> E[Snyk vulnerabilities fixed]
    E --> F[Project becomes more secure]
Loading

File-Level Changes

Change Details Files
Upgrade undici dependency to mitigate security vulnerabilities
  • Updated the version of undici from 5.11.0 to 5.28.5 in package.json
  • Addresses multiple security issues including ReDoS, Insecure Randomness, and others as highlighted by Snyk
apps/examples/solid-start/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants