[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
	Remote Memory Exposure SNYK-JS-DNSPACKET-1293563	387	No Known Exploit
	Prototype Pollution SNYK-JS-ASYNC-2441827	387	Proof of Concept
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	387	No Known Exploit
	Prototype Pollution SNYK-JS-IMMER-1019369	387	Proof of Concept
	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	387	Proof of Concept
	Improper Handling of Extra Parameters SNYK-JS-FOLLOWREDIRECTS-6141137	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
	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
	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	387	No Known Exploit
	Improper Handling of Unexpected Data Type SNYK-JS-ONHEADERS-10773729	387	No Known Exploit
	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
	Improper Input Validation SNYK-JS-URLPARSE-1078283	387	No Known Exploit
	Open Redirect SNYK-JS-URLPARSE-1533425	387	Proof of Concept
	Access Restriction Bypass SNYK-JS-URLPARSE-2401205	387	Proof of Concept
	Authorization Bypass Through User-Controlled Key SNYK-JS-URLPARSE-2412697	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
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-6444610	387	Proof of Concept
	Authorization Bypass SNYK-JS-URLPARSE-2407759	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, automatically generated by Snyk, focuses on improving the project's security posture by performing a routine upgrade of the react-scripts dependency. This update is crucial for mitigating a wide array of identified vulnerabilities and ensuring the application remains secure and up-to-date with the latest stable releases.

Highlights

• Dependency Upgrade: The react-scripts dependency has been upgraded from version 4.0.1 to 4.0.3.
• Security Vulnerability Resolution: This upgrade addresses a significant number of security vulnerabilities, including critical, high, medium, and low severity issues. These include, but are not limited to, Prototype Pollution, Remote Memory Exposure, Server-side Request Forgery (SSRF), Cross-site Scripting (XSS), and various forms of Improper Input Validation and Information Exposure.

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 or fill out our survey 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.

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, upgrades react-scripts from 4.0.1 to 4.0.3 to address several security vulnerabilities. While this is a positive change, I've recommended a further improvement in package.json. Specifically, I've suggested using semantic versioning with a caret (^) to allow for future non-breaking updates. More importantly, I've highlighted that react-scripts version 4 is outdated and strongly recommended planning an upgrade to the latest major version (5.x) to ensure long-term security and maintainability.

[gemini-code-assist]

While this upgrade is a good security improvement, I recommend two further changes for better long-term maintainability and security:

1. Use Semantic Versioning: The dependency is pinned to an exact version. Using a caret (^) (e.g., ^4.0.3) is a best practice to automatically receive non-breaking security patches and bug fixes in future npm install or yarn runs.

2. Plan a Major Version Upgrade: react-scripts v4 is outdated (this version is from early 2021) and likely no longer receiving security updates. The latest major version is 5.x. Upgrading to the latest stable version (e.g., ^5.0.1) should be prioritized to benefit from ongoing support, modern features, and crucial security updates. Sticking with an unmaintained major version poses a significant long-term risk.

For this PR, I've suggested at least adding the caret to the version.

    "react-scripts": "^4.0.3"