Skip to content

[Snyk] Upgrade react-scripts from 4.0.1 to 4.0.3 #39

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: master
Choose a base branch
from

Conversation

nejidevelops
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade react-scripts from 4.0.1 to 4.0.3.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released 4 years ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Remote Memory Exposure
SNYK-JS-DNSPACKET-1293563
305 No Known Exploit
high severity Improper Handling of Extra Parameters
SNYK-JS-FOLLOWREDIRECTS-6141137
305 Proof of Concept
high severity Prototype Pollution
SNYK-JS-ASYNC-2441827
305 Proof of Concept
high severity Asymmetric Resource Consumption (Amplification)
SNYK-JS-BODYPARSER-7926860
305 No Known Exploit
high severity Prototype Pollution
SNYK-JS-IMMER-1019369
305 Proof of Concept
high severity Server-side Request Forgery (SSRF)
SNYK-JS-IP-6240864
305 Proof of Concept
high severity Improper Input Validation
SNYK-JS-URLPARSE-2407770
305 Proof of Concept
medium severity Open Redirect
SNYK-JS-EXPRESS-6474509
305 No Known Exploit
medium severity Cross-site Scripting
SNYK-JS-EXPRESS-7926867
305 No Known Exploit
medium severity Command Injection
SNYK-JS-REACTDEVUTILS-1083268
305 Proof of Concept
medium severity Information Exposure
SNYK-JS-EVENTSOURCE-2823375
305 Proof of Concept
medium severity Cross-site Scripting (XSS)
SNYK-JS-COOKIE-8163060
305 No Known Exploit
medium severity Information Exposure
SNYK-JS-FOLLOWREDIRECTS-2332181
305 Proof of Concept
medium severity Information Exposure
SNYK-JS-FOLLOWREDIRECTS-6444610
305 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-7925106
305 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-8482416
305 Proof of Concept
medium severity Improper Input Validation
SNYK-JS-URLPARSE-1078283
305 No Known Exploit
medium severity Open Redirect
SNYK-JS-URLPARSE-1533425
305 Proof of Concept
medium severity Access Restriction Bypass
SNYK-JS-URLPARSE-2401205
305 Proof of Concept
medium severity Authorization Bypass
SNYK-JS-URLPARSE-2407759
305 Proof of Concept
medium severity Authorization Bypass Through User-Controlled Key
SNYK-JS-URLPARSE-2412697
305 Proof of Concept
low severity Cross-site Scripting
SNYK-JS-SEND-7926862
305 No Known Exploit
low severity Cross-site Scripting
SNYK-JS-SERVESTATIC-7926865
305 No Known Exploit
low severity Information Exposure
SNYK-JS-FOLLOWREDIRECTS-2396346
305 No Known Exploit
critical severity Incomplete List of Disallowed Inputs
SNYK-JS-BABELTRAVERSE-5962462
305 Proof of Concept
Release notes
Package name: react-scripts
  • 4.0.3 - 2021-02-22
  • 4.0.2 - 2021-02-03
  • 4.0.1 - 2020-11-23
from react-scripts GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade react-scripts from 4.0.1 to 4.0.3.

See this package in npm:
react-scripts

See this project in Snyk:
https://app.snyk.io/org/newtonombese1/project/8b459f2e-82b2-4c7d-9100-f989edb837b9?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @nejidevelops, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request upgrades the react-scripts dependency from version 4.0.1 to 4.0.3. This upgrade resolves multiple high and medium severity vulnerabilities, including remote memory exposure, prototype pollution, server-side request forgery, and cross-site scripting issues. The PR was automatically generated by Snyk.

Highlights

  • Dependency Upgrade: The pull request upgrades the react-scripts dependency in package.json from version 4.0.1 to 4.0.3.
  • Vulnerability Fixes: The upgrade addresses multiple security vulnerabilities, as identified by Snyk, including high and medium severity issues.
  • Automated PR: This pull request was automatically created by Snyk to keep dependencies up-to-date and address security concerns.

Changelog

  • package.json
    • Upgraded react-scripts dependency from version 4.0.1 to 4.0.3.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


A script's upgrade,
Averts potential dangers,
Code's peace is kept.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request upgrades the react-scripts dependency from version 4.0.1 to 4.0.3. The pull request description indicates that this upgrade resolves several security vulnerabilities, including some with high and critical severity. Given the nature of the changes, a thorough review is essential to ensure no regressions are introduced.

Summary of Findings

  • Security Vulnerabilities: The upgrade addresses multiple security vulnerabilities, including high and critical severity issues. It's crucial to verify that the upgrade is successful and doesn't introduce new issues.

Merge Readiness

Given that this pull request addresses several security vulnerabilities, including some with high and critical severity, it is highly recommended to merge these changes as soon as possible. However, due to the potential for unforeseen issues, it's important to ensure that thorough testing is performed after the upgrade to confirm that the application functions as expected. I am unable to approve this pull request, and users should have others review and approve this code before merging. I recommend that this pull request not be merged until a successful test has been performed.

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