Skip to content

[Snyk] Security upgrade electron from 25.8.2 to 25.9.4 #31123

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 Improper Input Validation
SNYK-JS-ELECTRON-6043905
No No Known Exploit
high severity Integer Overflow or Wraparound
SNYK-JS-ELECTRON-6043907
No No Known Exploit

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:

🦉 Improper Input Validation

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~01eaf20d851420644a
  • Upwork Job ID: 1722609692504813568
  • Last Price Increase: 2023-11-09

Activity

  1. added
    InternalRequires API changes or must be handled by Expensify staff
    on Nov 9, 2023
  2. melvin-bot commented on Nov 9, 2023

    @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 Nov 9, 2023

    @melvin-bot
    Author
  4. melvin-bot commented on Nov 9, 2023

    @melvin-bot
    Author

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

  5. melvin-bot commented on Dec 4, 2023

    @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!

  6. rlinoz commented on Dec 6, 2023

    @rlinoz
    Contributor

    Closing since the PR is merged

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 staffMonthlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions