[Snyk] Upgrade react-scripts from 4.0.1 to 4.0.3

[nejidevelops]

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
	Prototype Pollution SNYK-JS-IMMER-1019369	482	Proof of Concept
	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	482	Proof of Concept
	Improper Handling of Extra Parameters SNYK-JS-FOLLOWREDIRECTS-6141137	482	Proof of Concept
	Remote Memory Exposure SNYK-JS-DNSPACKET-1293563	482	No Known Exploit
	Prototype Pollution SNYK-JS-ASYNC-2441827	482	Proof of Concept
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	482	No Known Exploit
	Improper Input Validation SNYK-JS-URLPARSE-2407770	482	Proof of Concept
	Information Exposure SNYK-JS-EVENTSOURCE-2823375	482	Proof of Concept
	Open Redirect SNYK-JS-EXPRESS-6474509	482	No Known Exploit
	Cross-site Scripting SNYK-JS-EXPRESS-7926867	482	No Known Exploit
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-2332181	482	Proof of Concept
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-6444610	482	Proof of Concept
	Command Injection SNYK-JS-REACTDEVUTILS-1083268	482	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-8482416	482	Proof of Concept
	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	482	No Known Exploit
	Improper Input Validation SNYK-JS-URLPARSE-1078283	482	No Known Exploit
	Open Redirect SNYK-JS-URLPARSE-1533425	482	Proof of Concept
	Access Restriction Bypass SNYK-JS-URLPARSE-2401205	482	Proof of Concept
	Authorization Bypass SNYK-JS-URLPARSE-2407759	482	Proof of Concept
	Authorization Bypass Through User-Controlled Key SNYK-JS-URLPARSE-2412697	482	Proof of Concept
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-2396346	482	No Known Exploit
	Cross-site Scripting SNYK-JS-SEND-7926862	482	No Known Exploit
	Cross-site Scripting SNYK-JS-SERVESTATIC-7926865	482	No Known Exploit
	Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462	482	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:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[gemini-code-assist]

Hello @nejidevelops, I'm Gemini Code Assist¹! 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

Hello team, gemini-code-assist here to provide a summary of this pull request. This PR was automatically generated by Snyk to upgrade the react-scripts dependency from version 4.0.1 to 4.0.3. The primary goal of this upgrade is to address a significant number of security vulnerabilities identified in the current version, including several high and critical severity issues related to various underlying dependencies used by react-scripts. The PR description provides a detailed list of the specific vulnerabilities being fixed.

Highlights

• Security Fixes: This upgrade is intended to fix multiple security vulnerabilities, including high and critical severity issues, as detailed in the PR description provided by Snyk.

Changelog

• package.json
  • Updated the react-scripts dependency version from 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 version old,
Has stories of risks untold.
Upgrade, make it bold!

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. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, proposes an upgrade of the react-scripts package from version 4.0.1 to 4.0.3. This is a valuable change as it addresses a significant number of security vulnerabilities, including one critical (SNYK-JS-BABELTRAVERSE-5962462) and several high-severity issues, as detailed in the PR description.

Overall, the change is straightforward and beneficial from a security standpoint. However, due to the central role of react-scripts in a Create React App project, thorough testing is paramount before merging.

Key recommendations:

1. Comprehensive Testing: Before merging, please ensure this upgrade undergoes rigorous testing. This includes verifying that the application builds correctly, all unit and integration tests pass, and there are no regressions in functionality (manual QA might be necessary).
2. Future Considerations: While this upgrade is a good incremental step, react-scripts version 4.0.3 is from early 2021. It would be prudent to plan for an eventual migration to react-scripts 5.x to take advantage of newer features, updated dependencies (like Webpack 5), and more recent security enhancements. This is also highlighted in a review comment.

This PR is a positive contribution to the project's security and stability. As an AI reviewer, I am not authorized to approve pull requests. Please ensure it receives the necessary human review and passes all CI checks and testing phases.

Summary of Findings

• Security Vulnerability Remediation: This PR successfully upgrades react-scripts to version 4.0.3, addressing multiple security vulnerabilities, including one critical (SNYK-JS-BABELTRAVERSE-5962462) and numerous high/medium severity issues. This is a significant improvement to the project's security posture.
• Consideration for Future react-scripts Upgrade: The updated version [email protected] is from early 2021. While this PR is beneficial, planning an upgrade to react-scripts 5.x in the future is advisable to leverage newer features, more current dependencies, and ongoing support. This was also noted in a review comment with medium severity.
• Critical Need for Testing: Given that react-scripts is a fundamental dependency for the build system and development environment, thorough testing (build process, automated tests, and manual QA) is essential before merging this PR to ensure no regressions or unexpected issues are introduced.

Merge Readiness

This pull request is a positive step towards improving the security of the application by upgrading react-scripts. The change itself is minimal and targets known vulnerabilities effectively.

Before merging, it is critical to perform comprehensive testing to confirm that the application builds, runs, and functions as expected with the new version of react-scripts. This includes running all automated tests and potentially some manual quality assurance.

One medium severity comment has been made regarding the age of the react-scripts 4.x line and encourages consideration of an upgrade to 5.x in the future for longer-term benefits. This does not block the current PR but is a point for future planning.

Assuming thorough testing is successful, this PR is recommended for merging to address the identified security risks. As an AI, I cannot approve PRs; please ensure it undergoes the standard review and approval process within your team.

[gemini-code-assist]

This upgrade to [email protected] is a good and necessary step for addressing the listed security vulnerabilities.

It's worth noting that this version was released in early 2021, and react-scripts 4.x is an older major version line. The latest stable major version is 5.x.x.

For future planning, have you considered or is there a roadmap for migrating to react-scripts 5.x? Such an upgrade, while potentially more involved, would bring benefits like:

• More up-to-date underlying dependencies (e.g., Webpack 5, Babel 7, PostCSS 8).
• Access to newer features and performance improvements from the Create React App team.
• Potentially a more robust long-term security posture.

For this PR, the update to 4.0.3 is a solid incremental improvement. Ensuring thorough testing after this change is crucial.