Skip to content

[Snyk] Fix for 4 vulnerabilities #233

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

Open
wants to merge 1 commit into
base: CircleCI-v2
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/run-in-electron/package.json

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
high severity 696/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS)
SNYK-JS-ANSIREGEX-1583908
Yes Proof of Concept
high severity 726/1000
Why? Recently disclosed, Has a fix available, CVSS 8.8
Use After Free
SNYK-JS-ELECTRON-6226524
Yes No Known Exploit
medium severity 646/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.5
Server-side Request Forgery (SSRF)
SNYK-JS-REQUEST-3361831
Yes Proof of Concept
medium severity 646/1000
Why? Proof of Concept exploit, Has a fix available, CVSS 6.5
Prototype Pollution
SNYK-JS-TOUGHCOOKIE-5672873
Yes Proof of Concept

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

Commit messages
Package name: electron-rebuild The new version differs by 250 commits.
  • 6f94aaa Merge pull request #1022 from VerteDinde/add-std17-flag-for-e20
  • 3f5ff99 fix: ensure force-process-config is not passed to prerelease v20+ (#1023)
  • 979361d fix: add std=c++17 flag for e20+
  • 20107a8 Merge pull request #1015 from electron/dependabot/npm_and_yarn/typescript-4.6.4
  • 3108e3d chore(deps-dev): bump typescript from 4.6.2 to 4.6.4
  • 00e6ed3 Merge pull request #1014 from electron/dependabot/npm_and_yarn/types/node-17.0.34
  • f9d77d2 chore(deps-dev): bump @ types/node from 17.0.33 to 17.0.34
  • f3342e2 Merge pull request #1003 from electron/dependabot/npm_and_yarn/yargs-17.4.1
  • 41fa566 Merge pull request #1013 from electron/dependabot/npm_and_yarn/types/node-17.0.33
  • 9b3be7c chore(deps-dev): bump @ types/node from 17.0.21 to 17.0.33
  • 641db3d chore(deps): bump yargs from 17.3.1 to 17.4.1
  • e677ce6 Merge pull request #993 from electron/dependabot/npm_and_yarn/ts-node-10.7.0
  • 3cb7db1 Merge pull request #995 from electron/dependabot/npm_and_yarn/mocha-9.2.2
  • 2facce0 chore(deps-dev): bump mocha from 9.2.0 to 9.2.2
  • 0e59898 chore(deps-dev): bump ts-node from 10.6.0 to 10.7.0
  • 4d54c15 Merge pull request #990 from electron/dependabot/npm_and_yarn/types/yargs-17.0.9
  • 1b45c84 Merge pull request #991 from electron/dependabot/npm_and_yarn/ts-node-10.6.0
  • 708a1c4 Merge pull request #992 from electron/dependabot/npm_and_yarn/node-gyp-9.0.0
  • 6d61b02 chore(deps): bump node-gyp from 8.4.1 to 9.0.0
  • 7c01ce3 chore(deps-dev): bump ts-node from 10.5.0 to 10.6.0
  • 8adb090 chore(deps-dev): bump @ types/yargs from 17.0.8 to 17.0.9
  • f798bc5 Merge pull request #986 from electron/dependabot/npm_and_yarn/fs-extra-10.0.1
  • 2df36e0 Merge pull request #987 from electron/dependabot/npm_and_yarn/types/node-17.0.21
  • f4edeb5 Merge pull request #988 from electron/dependabot/npm_and_yarn/typescript-4.6.2

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Use After Free
🦉 Server-side Request Forgery (SSRF)
🦉 More lessons are available in Snyk Learn

Copy link

google-cla bot commented Feb 3, 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/[email protected] environment, filesystem, network, shell +84 16.9 MB electron-cfa
npm/[email protected] Transitive: environment, filesystem, network, shell +44 6.25 MB electron-nightly, electronhq

🚮 Removed packages: npm/[email protected], npm/[email protected]

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
Native code npm/[email protected]

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

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/[email protected] or ignore all packages with @SocketSecurity ignore-all

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

Successfully merging this pull request may close these issues.

2 participants