Skip to content

[Snyk] Security upgrade @storybook/react from 6.5.10 to 7.0.0 #36332

Closed

Description

@melvin-bot

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


Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

  • Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
    • package.json
    • package-lock.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Issue Breaking Change Exploit Maturity
high severity Server-side Request Forgery (SSRF)
SNYK-JS-IP-6240864
Yes Proof of Concept
Commit messages
Package name: @storybook/react The new version differs by 250 commits.

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.


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

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01c4916a5e7b404cb1
  • Upwork Job ID: 1757029477245767680
  • Last Price Increase: 2024-02-12

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Feb 12, 2024
  2. melvin-bot commented on Feb 12, 2024

    @melvin-bot
    Author

    This is a Snyk issue. Snyk is a tool that automatically tracks our repositories' dependencies and reports associated security vulnerabilities. It also automatically create PRs to fix these vulnerabilities.

        C+: Please follow these steps to test the linked PR before running through the reviewer checklist:
        - [ ] The first step is to understand the PR: what dependency is it upgrading, for which vulnerability, how it impacts our product & end users.
        - [ ] If the issue is not worth fixing, please add your reasoning in the issue and have the internal engineer review it.
        - [ ] Check the change log (which should be included in the PR description) to see all changes. We want to identify any breaking changes. If it is a minor version bump, it's unlikely that there are any breaking changes.
        - [ ] Test our feature(s) that make use of this package. If it does not work, we should understand what broke it. It is also a good idea to check our main flows to make sure they are not broken that you can add in the checklist screenshots/videos.
    
  3. melvin-bot commented on Feb 12, 2024

    @melvin-bot
    Author
  4. melvin-bot commented on Feb 12, 2024

    @melvin-bot
    Author

    Triggered auto assignment to Contributor Plus for review of internal employee PR - @akinwale (Internal)

  5. levpachmanov commented on Feb 12, 2024

    @levpachmanov

    Hi @akinwale,

    Unfortunately, the library node-ip is no longer maintained, so there is no public solution.

    We're part of a startup called Seal Security that mitigates software vulnerabilities in older open source versions by backporting/creating standalone security patches - enabling more straightforward remediation in cases like this. We created an ip 1.1.8-sp and 2.0.0-sp1 that's vulnerability-free. As with all of our patches, it's open-source and available for free.

    If relevant, check out our GitHub repo if you wish to learn more, or start using our app.

    Please feel free to reach us at info@seal.security if you have any requests/questions.

  6. melvin-bot commented on Feb 12, 2024

    @melvin-bot
    Author

    📣 @levpachmanov! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  7. melvin-bot commented on Mar 6, 2024

    @melvin-bot
    Author

    This issue has not been updated in over 15 days. @akinwale eroding to Monthly issue.

    P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

  8. melvin-bot commented on May 20, 2024

    @melvin-bot
    Author

    @akinwale, this Monthly task hasn't been acted upon in 6 weeks; closing.

    If you disagree, feel encouraged to reopen it -- but pick your least important issue to close instead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

InternalRequires API changes or must be handled by Expensify staffMonthlyKSv2Not a priority

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions