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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Security upgrade react-native from 0.57.3 to 0.69.12 #133

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

Conversation

titanism
Copy link
Contributor

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 `yarn` dependencies of this project.

Changes included in this PR

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

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed

With an upgrade:
Severity Priority Score (*) Issue Breaking Change Exploit Maturity
medium severity 718/1000
Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 6.5
Uncontrolled Resource Consumption ('Resource Exhaustion')
SNYK-JS-TAR-6476909
No Proof of Concept

(*) 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:

🦉 Uncontrolled Resource Consumption ('Resource Exhaustion')

Copy link

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@babel/[email protected] None 0 6.57 kB hzoo
npm/@babel/[email protected] None +2 13.4 kB hzoo
npm/@babel/[email protected] None +1 10.4 kB hzoo
npm/@babel/[email protected] None 0 4.15 kB hzoo
npm/@babel/[email protected] None +6 87.3 kB hzoo
npm/@babel/[email protected] None +2 11.8 kB hzoo
npm/@babel/[email protected] None 0 3.45 kB hzoo
npm/@babel/[email protected] None 0 8.7 kB hzoo
npm/@babel/[email protected] None +3 19.6 kB hzoo
npm/@babel/[email protected] None +2 22.6 kB hzoo
npm/[email protected] None 0 4.78 kB isaacs
npm/[email protected] None 0 16.6 kB dougwilson
npm/[email protected] None 0 564 kB marijn
npm/[email protected] None 0 8.18 kB iarna
npm/[email protected] None 0 6.88 kB jonschlinkert
npm/[email protected] environment 0 11.4 kB pfmooney
npm/[email protected] None 0 541 kB aearly
npm/[email protected] None +3 123 kB hzoo
npm/[email protected] filesystem Transitive: environment +5 39.2 kB mjesun
npm/[email protected] environment +27 212 kB gweterings
npm/[email protected] None 0 46.8 kB hzoo
npm/[email protected] None +1 288 kB hzoo
npm/[email protected] environment +10 522 kB hzoo
npm/[email protected] None +1 143 kB hzoo
npm/[email protected] None 0 13 kB feross
npm/[email protected] None 0 99.4 kB indutny
npm/[email protected] None +1 34.6 kB cwmma
npm/[email protected] None 0 1.23 MB ai
npm/[email protected] None 0 7.95 kB cwmma
npm/[email protected] None 0 3.15 kB sindresorhus
npm/[email protected] None 0 14.2 kB sindresorhus
npm/[email protected] filesystem, shell 0 62.4 kB abetomo
npm/[email protected] None +1 14.5 kB mafintosh
npm/[email protected] None 0 12.7 kB iarna
npm/[email protected] eval 0 2.18 MB zloirock
npm/[email protected] None 0 23.2 kB isaacs
npm/[email protected] None 0 5.21 kB cwmma
npm/[email protected] None 0 5.81 kB cwmma
npm/[email protected] environment, filesystem, shell 0 16.7 kB satazor
npm/[email protected] None 0 58.2 kB nv
npm/[email protected] environment, filesystem, shell 0 17.2 kB lovell
npm/[email protected] None 0 17.1 kB mafintosh
npm/[email protected] None 0 20.1 kB kilianvalkhof
npm/[email protected] None 0 5.87 kB mafintosh
npm/[email protected] None 0 18 kB ralphtheninja
npm/[email protected] None 0 33 kB nzakas
npm/[email protected] None 0 49.3 kB michaelficarra
npm/[email protected] None 0 5.13 kB dcousens
npm/[email protected] None 0 22.8 kB dap
npm/[email protected] None 0 8.89 kB sindresorhus
npm/[email protected] None 0 2.86 MB flowtype
npm/[email protected] None 0 6.28 kB jonschlinkert
npm/[email protected] filesystem 0 13 kB iarna
npm/[email protected] Transitive: environment +2 60.8 kB iarna
npm/[email protected] None 0 3.71 kB jonschlinkert
npm/[email protected] filesystem Transitive: environment +2 72.7 kB isaacs
npm/[email protected] environment, filesystem 0 24.9 kB isaacs
npm/[email protected] None 0 40.2 kB indutny
npm/[email protected] environment, filesystem, network Transitive: eval, shell +136 25.7 MB thymikee
npm/[email protected] None 0 13.1 kB mridgway
npm/[email protected] Transitive: environment, eval +1 46.3 kB dougwilson
npm/[email protected] None 0 336 kB ashtuchkin
npm/[email protected] filesystem 0 10.8 kB isaacs
npm/[email protected] None 0 3.82 kB isaacs
npm/[email protected] None 0 8.93 kB isaacs
npm/[email protected] None 0 30.6 kB ljharb
npm/[email protected] None +2 27.2 kB jonschlinkert
npm/[email protected] None 0 4.17 kB jonschlinkert
npm/[email protected] None 0 5.92 kB jonschlinkert
npm/[email protected] None 0 3.23 kB sindresorhus
npm/[email protected] None 0 21.8 kB coreyfarrell
npm/[email protected] None +1 338 kB coreyfarrell
npm/[email protected] filesystem Transitive: environment +1 103 kB coreyfarrell
npm/[email protected] None +1 5.73 kB mjesun

🚮 Removed packages: npm/@commitlint/[email protected], npm/@commitlint/[email protected], npm/@types/[email protected], npm/@types/[email protected], npm/@typescript-eslint/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], npm/[email protected], 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
Known Malware npm/[email protected]
  • Note: This package downloads prebuilt artifacts from a domain which has been compromised. Your system may be infected if you installed this package prior to April 27, 2023
Install scripts npm/[email protected]
  • Install script: install
  • Source: node install

View full report↗︎

Next steps

What is known malware?

This package is malware. We have asked the package registry to remove it.

It is strongly recommended that malware is removed from your codebase.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants