[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
	Improper Handling of Extra Parameters SNYK-JS-FOLLOWREDIRECTS-6141137	432	Proof of Concept
	Prototype Pollution SNYK-JS-ASYNC-2441827	432	Proof of Concept
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	432	No Known Exploit
	Remote Memory Exposure SNYK-JS-DNSPACKET-1293563	432	No Known Exploit
	Prototype Pollution SNYK-JS-IMMER-1019369	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
	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
	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	432	No Known Exploit
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-2396346	432	No Known Exploit
	Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462	432	Proof of Concept
	Command Injection SNYK-JS-REACTDEVUTILS-1083268	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
	Improper Handling of Unexpected Data Type SNYK-JS-ONHEADERS-10773729	432	No Known Exploit
	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 SNYK-JS-SEND-7926862	432	No Known Exploit
	Cross-site Scripting SNYK-JS-SERVESTATIC-7926865	432	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 enhancing the project's security by updating the react-scripts dependency. The upgrade to version 4.0.3 is crucial for resolving a substantial number of identified vulnerabilities, ensuring the application benefits from the latest security patches and maintains a robust defense against potential threats.

Highlights

• Dependency Upgrade: Upgraded the react-scripts dependency from version 4.0.1 to 4.0.3.
• Security Vulnerability Resolution: This upgrade addresses a total of 26 known vulnerabilities, including 1 critical-severity, 7 high-severity, 15 medium-severity, and 3 low-severity issues, significantly improving the project's security posture.

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 upgrades react-scripts from 4.0.1 to 4.0.3, which is a good step as it resolves multiple security vulnerabilities. However, the react-scripts package is still significantly outdated. I've added a comment suggesting a further upgrade to the latest version (5.0.1) to improve the project's security posture and long-term maintainability. This major version upgrade will require careful testing.

[gemini-code-assist]

While upgrading react-scripts from 4.0.1 to 4.0.3 is a good step to resolve several vulnerabilities, this version is still quite old (from early 2021) and may contain other security issues. The latest stable version is 5.0.1.

I recommend upgrading to the latest version to ensure your project has the most recent features, bug fixes, and security patches. Upgrading to a major version like 5.x might require addressing some breaking changes, so it should be tested carefully.

Suggested change

	"react-scripts": "4.0.3"
	"react-scripts": "5.0.1"