[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	452	No Known Exploit
	Improper Input Validation SNYK-JS-URLPARSE-2407770	452	Proof of Concept
	Prototype Pollution SNYK-JS-IMMER-1019369	452	Proof of Concept
	Server-side Request Forgery (SSRF) SNYK-JS-IP-6240864	452	Proof of Concept
	Improper Handling of Extra Parameters SNYK-JS-FOLLOWREDIRECTS-6141137	452	Proof of Concept
	Prototype Pollution SNYK-JS-ASYNC-2441827	452	Proof of Concept
	Asymmetric Resource Consumption (Amplification) SNYK-JS-BODYPARSER-7926860	452	No Known Exploit
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-7925106	452	Proof of Concept
	Regular Expression Denial of Service (ReDoS) SNYK-JS-PATHTOREGEXP-8482416	452	Proof of Concept
	Command Injection SNYK-JS-REACTDEVUTILS-1083268	452	Proof of Concept
	Information Exposure SNYK-JS-EVENTSOURCE-2823375	452	Proof of Concept
	Open Redirect SNYK-JS-EXPRESS-6474509	452	No Known Exploit
	Cross-site Scripting SNYK-JS-EXPRESS-7926867	452	No Known Exploit
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-2332181	452	Proof of Concept
	Improper Input Validation SNYK-JS-URLPARSE-1078283	452	No Known Exploit
	Open Redirect SNYK-JS-URLPARSE-1533425	452	Proof of Concept
	Access Restriction Bypass SNYK-JS-URLPARSE-2401205	452	Proof of Concept
	Authorization Bypass SNYK-JS-URLPARSE-2407759	452	Proof of Concept
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-6444610	452	Proof of Concept
	Authorization Bypass Through User-Controlled Key SNYK-JS-URLPARSE-2412697	452	Proof of Concept
	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	452	No Known Exploit
	Information Exposure SNYK-JS-FOLLOWREDIRECTS-2396346	452	No Known Exploit
	Cross-site Scripting SNYK-JS-SERVESTATIC-7926865	452	No Known Exploit
	Incomplete List of Disallowed Inputs SNYK-JS-BABELTRAVERSE-5962462	452	Proof of Concept
	Cross-site Scripting SNYK-JS-SEND-7926862	452	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 is an automated security update, initiated by Snyk, aimed at improving the project's overall security posture. It focuses on updating a critical development dependency to resolve a comprehensive list of known vulnerabilities, ensuring the application benefits from the latest security patches and improvements.

Highlights

• Dependency Upgrade: This pull request upgrades the react-scripts dependency from version 4.0.1 to 4.0.3.
• Security Vulnerability Resolution: The upgrade addresses a significant number of identified security vulnerabilities, including several high-severity issues such as Remote Memory Exposure, Improper Input Validation, Prototype Pollution, and Server-side Request Forgery (SSRF), as well as various medium and low-severity concerns.

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.

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 version 4.0.1 to 4.0.3. This is a patch update that addresses a number of security vulnerabilities, including one critical vulnerability.

The change is correct and beneficial. I've added a comment on package.json with two recommendations:

1. To change the version specifier to ^4.0.3 to automatically receive future non-breaking security patches.
2. To plan a follow-up upgrade to [email protected] to resolve other known vulnerabilities and keep the project up-to-date, which will also require upgrading React itself.

After applying the change, please remember to run npm install to update package-lock.json and commit the result.

[gemini-code-assist]

Thank you for addressing these vulnerabilities. This upgrade from 4.0.1 to 4.0.3 is a good step as it resolves several security issues, including a critical one.

I have two suggestions for further improvement:

1. Use a caret ^ for the version: To automatically get non-breaking security patches in the future, it's a good practice to use a caret ^ for the version specifier, similar to react and react-dom in this file. This would change "4.0.3" to "^4.0.3".

2. Plan an upgrade to version 5: [email protected] is still outdated and has known vulnerabilities (e.g., those fixed in 5.0.1). I strongly recommend planning a follow-up to upgrade to [email protected]. This is a major version bump and will require upgrading react and react-dom to v18, but it's crucial for security and maintainability.

For this PR, I'd suggest applying the first point.

    "react-scripts": "^4.0.3"