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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade electron from 12.2.3 to 29.3.0 #778

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

Conversation

adamlaska
Copy link
Owner

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:
    • examples/with-electron/package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Improper Restriction of Operations within the Bounds of a Memory Buffer
SNYK-JS-ELECTRON-6579648
Yes No Known Exploit

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

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:

馃 Learn about vulnerability in an interactive lesson of Snyk Learn.

Copy link

google-cla bot commented Apr 15, 2024

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub 鈫楋笌

Package New capabilities Transitives Size Publisher
npm/@apollo/client@3.9.11 network Transitive: environment, eval +16 8.92 MB apollo-bot
npm/@babel/types@7.18.0 environment +2 1.1 MB nicolo-ribaudo
npm/@graphql-yoga/node@2.13.13 environment, network Transitive: filesystem, unsafe +31 13.6 MB dotansimha
npm/@types/cors@2.8.17 None 0 5.91 kB types
npm/@types/node@18.19.31 None +1 2.04 MB types
npm/@types/react-dom@18.2.25 None 0 34.9 kB types
npm/@types/react@17.0.37 None +1 183 kB types
npm/@types/react@18.2.78 None +2 1.69 MB types
npm/@types/uuid@8.3.4 None 0 6.67 kB types
npm/async-sema@3.1.1 None 0 13.5 kB leerobinson
npm/cookie@0.5.0 None 0 23.1 kB dougwilson
npm/cross-env@7.0.3 environment Transitive: filesystem, shell +6 81.2 kB kentcdodds
npm/fs-extra@10.0.0 Transitive: filesystem +2 156 kB ryanzim
npm/fs-extra@8.1.0 filesystem Transitive: environment +3 182 kB ryanzim
npm/graphql@14.7.0 None +1 1.92 MB i1g
npm/graphql@15.0.0 None 0 1.89 MB i1g
npm/lru-cache@7.18.3 None 0 134 kB isaacs
npm/next@12.0.7 environment, filesystem, network, shell, unsafe Transitive: eval +220 543 MB vercel-release-bot
npm/next@14.2.1 environment, filesystem, network, shell, unsafe +23 1.2 GB vercel-release-bot
npm/prettier@1.19.1 environment, eval, filesystem, unsafe 0 9.57 MB lydell
npm/pretty-ms@5.1.0 None +1 15.4 kB sindresorhus
npm/pretty-ms@7.0.1 None 0 12 kB sindresorhus
npm/prop-types@15.8.1 environment +2 124 kB ljharb
npm/react-dom@17.0.2 environment +2 3.11 MB gaearon
npm/react-dom@18.2.0 environment +3 4.62 MB gnoff
npm/react@17.0.2 environment +1 297 kB gaearon
npm/rimraf@3.0.2 filesystem 0 17.3 kB isaacs
npm/semver@7.3.4 None +2 116 kB isaacs
npm/uuid@8.1.0 None 0 95.2 kB ctavan
npm/uuid@8.3.2 None 0 116 kB ctavan
npm/yargs@16.2.0 environment, filesystem +15 623 kB oss-bot

馃毊 Removed packages: npm/acorn@8.11.3, npm/classnames@2.3.1, npm/classnames@2.5.1, npm/date-fns@2.28.0

View full report鈫楋笌

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.

Alert Package NoteSource
Telemetry npm/next@12.0.7
  • Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information
Telemetry npm/next@14.2.1
  • Note: Can be disabled by setting the environment variable NEXT_TELEMETRY_DISABLED=1 . See https://nextjs.org/telemetry for more information

View full report鈫楋笌

Next steps

What is telemetry?

This package contains telemetry which tracks how it is used.

Most telemetry comes with settings to disable it. Consider disabling telemetry if you do not want to be tracked.

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 ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

  • @SocketSecurity ignore npm/next@12.0.7
  • @SocketSecurity ignore npm/next@14.2.1

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