[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 5 years ago.

Issues fixed by the recommended upgrade:

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

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]

Summary of Changes

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!

This pull request automates a critical security update by upgrading the react-scripts dependency. The primary goal is to enhance the project's security posture by patching a wide array of known vulnerabilities, ensuring the application remains robust against potential exploits.

Highlights

• Dependency Upgrade: Upgraded the react-scripts dependency from version 4.0.1 to 4.0.3.
• Security Vulnerability Fixes: This upgrade addresses multiple high, medium, and low severity security vulnerabilities, including Prototype Pollution, Asymmetric Resource Consumption, Remote Memory Exposure, Improper Handling of Extra Parameters, Server-side Request Forgery (SSRF), Cross-site Scripting (XSS), Command Injection, Information Exposure, Open Redirect, Improper Input Validation, Access Restriction Bypass, Authorization Bypass, Regular Expression Denial of Service (ReDoS), and Incomplete List of Disallowed Inputs.

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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

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 from Snyk upgrades react-scripts from 4.0.1 to 4.0.3, which is a valuable security update that resolves numerous vulnerabilities, including a critical one. The change is correct and I recommend merging it.

I've added one medium severity suggestion on package.json to consider using a caret (^) for the react-scripts version. This would enable automatic non-breaking security updates, though it's a trade-off with the absolute stability provided by pinning the version, which is the default for Create React App projects.

More importantly, please note that react-scripts@4.x is significantly outdated. I strongly recommend planning a migration to the latest major version (5.x) to benefit from modern features, performance improvements, and a much broader range of security fixes.

[gemini-code-assist]

While pinning dependencies ensures build stability (the default for Create React App), consider using a caret (^) for react-scripts. This would automatically apply non-breaking security patches and bug fixes within the 4.x range, aligning its versioning with react and react-dom in this file and improving long-term security with minimal effort. This is a trade-off between maximum stability and automatic security updates.

Suggested change

	"react-scripts": "4.0.3"
	"react-scripts": "^4.0.3"