[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	432	Proof of Concept
	Improper Handling of Extra Parameters SNYK-JS-FOLLOWREDIRECTS-6141137	432	Proof of Concept
	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	432	Proof of Concept
	Improper Input Validation SNYK-JS-URLPARSE-2407770	432	Proof of Concept
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	432	No Known Exploit
	Prototype Pollution SNYK-JS-ASYNC-2441827	432	Proof of Concept
	Remote Memory Exposure SNYK-JS-DNSPACKET-1293563	432	No Known Exploit
	Information Exposure SNYK-JS-EVENTSOURCE-2823375	432	Proof of Concept
	Open Redirect SNYK-JS-EXPRESS-6474509	432	No Known Exploit
	Cross-site Scripting SNYK-JS-EXPRESS-7926867	432	No Known Exploit
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-2332181	432	Proof of Concept
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-6444610	432	Proof of Concept
	Improper Input Validation SNYK-JS-URLPARSE-1078283	432	No Known Exploit
	Open Redirect SNYK-JS-URLPARSE-1533425	432	Proof of Concept
	Access Restriction Bypass SNYK-JS-URLPARSE-2401205	432	Proof of Concept
	Authorization Bypass SNYK-JS-URLPARSE-2407759	432	Proof of Concept
	Authorization Bypass Through User-Controlled Key SNYK-JS-URLPARSE-2412697	432	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	432	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-8482416	432	Proof of Concept
	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	432	No Known Exploit
	Command Injection SNYK-JS-REACTDEVUTILS-1083268	432	Proof of Concept
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-2396346	432	No Known Exploit
	Cross-site Scripting SNYK-JS-SEND-7926862	432	No Known Exploit
	Cross-site Scripting SNYK-JS-SERVESTATIC-7926865	432	No Known Exploit
	Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462	432	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 with a summary of this pull request. This PR was automatically generated by Snyk to address several security vulnerabilities by upgrading the react-scripts dependency. The upgrade is from version 4.0.1 to 4.0.3. According to the Snyk description, this update fixes a number of high, medium, low, and even a critical severity vulnerability found in the current version.

Highlights

• Security Fixes: This upgrade is intended to fix multiple security vulnerabilities identified by Snyk, including critical, high, medium, and low severity issues.

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.

---

Dependencies age fast,
Security holes appear,
Upgrade keeps code safe.

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 Snyk-generated pull request to upgrade react-scripts from 4.0.1 to 4.0.3 is a positive security measure, addressing a number of vulnerabilities including one critical and several high/medium severity issues. Thank you for addressing these.

Given that react-scripts is a core dependency managing the build system, testing, and development server, it's crucial to ensure this upgrade doesn't introduce any regressions. I've added a specific comment regarding this and the age of the target version.

Summary of Findings

• Security Improvement: The upgrade to react-scripts 4.0.3 addresses multiple security vulnerabilities, which is a significant benefit.
• Comprehensive Testing Required: As react-scripts is a critical build dependency, thorough testing (unit, integration, E2E, and manual QA) is essential to ensure this upgrade does not introduce regressions or build issues.
• Dependency Age and Future Upgrade: react-scripts version 4.0.3, while an improvement, was released approximately 4 years ago. It's recommended to plan a future upgrade to a more current major version (e.g., 5.x.x) to benefit from the latest features, fixes, and security updates, and to reduce technical debt.

Merge Readiness

This pull request is a valuable security update by upgrading react-scripts. However, due to the critical nature of this dependency, comprehensive testing is paramount before merging to ensure no regressions are introduced. Furthermore, the target version 4.0.3 is itself quite dated. While this PR should proceed after successful testing, I strongly recommend creating a follow-up task to upgrade react-scripts to a more modern major version (e.g., v5.x) to maintain long-term project health and security. I am unable to approve this PR directly; please ensure thorough testing is completed and acknowledged by the team before merging.

[gemini-code-assist]

This upgrade to [email protected] is a good step for addressing the listed vulnerabilities. However, it's important to acknowledge that version 4.0.3 itself was released approximately 4 years ago (February 2021), as noted in the PR description. The current stable major version of react-scripts is 5.x.x.

Could we consider the following before merging or shortly after?

• Thorough Testing: Please ensure this upgrade is thoroughly tested across the application. This includes running all unit and integration tests, performing E2E tests if available, and conducting manual QA on critical user flows. react-scripts updates, even patch versions, can sometimes introduce subtle breaking changes due to the large number of underlying dependencies they manage (Webpack, Babel, Jest, etc.).
• Future Upgrade Plan: It would be beneficial to plan a follow-up task to upgrade react-scripts to a more recent major version (e.g., v5.x). This will provide access to newer features, bug fixes, performance improvements, and broader, more current security patch coverage. Staying on a significantly outdated major version can accumulate technical debt and increase security risks over time.

What are your thoughts on these points?