Skip to content

[Snyk] Fix for 3 vulnerabilities #38312

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 Denial of Service (DoS)
SNYK-JS-ELECTRON-6405830
No No Known Exploit
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
Yes Proof of Concept
high severity Prototype Pollution
SNYK-JS-UNSETVALUE-2400660
Yes No Known Exploit
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:

🦉 Denial of Service (DoS)
🦉 Prototype Pollution

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~017f0044a167283b00
  • Upwork Job ID: 1768276781396721664
  • Last Price Increase: 2024-03-14

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Mar 14, 2024
  2. melvin-bot commented on Mar 14, 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 Mar 14, 2024

    @melvin-bot
    Author
  4. melvin-bot commented on Mar 14, 2024

    @melvin-bot
    Author

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

  5. allroundexperts commented on Apr 1, 2024

    @allroundexperts
    Contributor

    @yuwenmemon Since the original PR had conflicts, I created a new one #39372. Can you please review / merge?

  6. self-assigned this
    on Apr 1, 2024
  7. yuwenmemon commented on Apr 19, 2024

    @yuwenmemon
    Contributor

    This was deployed to prod.

  8. allroundexperts commented on Apr 19, 2024

    @allroundexperts
    Contributor

    @yuwenmemon My compensation is pending here. Also, since this involved up-gradation of storybook (Took quite some time as evident from the merged PR), I would like to request a compensation of $500. Please review the request. Thanks!

  9. 2 remaining items

  10. melvin-bot commented on Apr 19, 2024

    @melvin-bot
    Author

    Triggered auto assignment to @greg-schroeder (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  11. removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Apr 19, 2024
  12. yuwenmemon commented on Apr 19, 2024

    @yuwenmemon
    Contributor

    @greg-schroeder Can you handle @allroundexperts's request above?

  13. melvin-bot commented on Apr 26, 2024

    @melvin-bot
    Author

    @yuwenmemon, @greg-schroeder, @allroundexperts Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  14. melvin-bot commented on Apr 30, 2024

    @melvin-bot
    Author

    @yuwenmemon, @greg-schroeder, @allroundexperts 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

  15. melvin-bot commented on May 2, 2024

    @melvin-bot
    Author

    @yuwenmemon, @greg-schroeder, @allroundexperts 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

  16. yuwenmemon commented on May 2, 2024

    @yuwenmemon
    Contributor

    @greg-schroeder any update on this one?

  17. greg-schroeder commented on May 9, 2024

    @greg-schroeder
    Contributor

    Apologies for the delay on this, for some reason my GH<>Slack zap isn't picking up my mentions on this issue 🤔

    Also it's better to add Awaiting Payment label or [HOLD for payment] in the title so it's easier to see this is waiting for payment, as that's how we generally filter them on the BZ team.

  18. greg-schroeder commented on May 9, 2024

    @greg-schroeder
    Contributor

    Creating a payment issue to generate a new upwork job and will send a manual offer: #41875

  19. greg-schroeder commented on May 9, 2024

    @greg-schroeder
    Contributor

    Oh, you're a NewDot-eligible C+. So, yeah, ignore that. You can make a manual request for $500 for this issue and link to this comment for confirmation.

  20. JmillsExpensify commented on Jun 28, 2024

    @JmillsExpensify
    Contributor

    $500 approved for @allroundexperts

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

Metadata

Metadata

Labels

DailyKSv2InternalRequires API changes or must be handled by Expensify staffReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions