[Snyk] Security upgrade webpack-dev-server from 3.1.4 to 4.8.0

[saurabharch]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• packages/react-scripts/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12704893	788
	Server-side Request Forgery (SSRF) SNYK-JS-IP-12761655	788

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Server-side Request Forgery (SSRF)

[gemini-code-assist]

Summary of Changes

Hello @saurabharch, 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, aims to enhance the project's security posture by updating a critical development dependency. It specifically targets and resolves two high-severity Server-side Request Forgery vulnerabilities found in webpack-dev-server, ensuring the application is protected against these potential security threats by moving to a patched version.

Highlights

• Dependency Upgrade: Upgraded the webpack-dev-server dependency from version "3.1.4" to "4.8.0".
• Security Fixes: This upgrade addresses two high-severity Server-side Request Forgery (SSRF) vulnerabilities, identified as SNYK-JS-IP-12704893 and SNYK-JS-IP-12761655.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description

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 PR upgrades webpack-dev-server to v4.8.0 to address security vulnerabilities. However, this is a major version upgrade with significant breaking changes. The current implementation will break the development server (npm start or yarn start). I've added a critical comment detailing the necessary code changes in packages/react-scripts/scripts/start.js and packages/react-scripts/config/webpackDevServer.config.js to make the project compatible with webpack-dev-server v4.

[gemini-code-assist]

Upgrading webpack-dev-server to version 4.x is a major breaking change that will cause the development server to fail with the current configuration.

The following files need to be updated to be compatible with webpack-dev-server v4:

1. packages/react-scripts/scripts/start.js:

   • The WebpackDevServer constructor arguments have been swapped. On line 109, new WebpackDevServer(compiler, serverConfig) must be changed to new WebpackDevServer(serverConfig, compiler).

2. packages/react-scripts/config/webpackDevServer.config.js:

   • disableHostCheck and public: These are removed. Use allowedHosts instead. The logic for setting this needs to be migrated carefully from the old options.
   • clientLogLevel: Renamed to client.logging. For example, clientLogLevel: 'none' becomes client: { logging: 'none' }.
   • contentBase: Removed. Use static: { directory: ... }.
   • watchContentBase: Removed. Use static: { watch: ... }.
   • publicPath: Moved to devMiddleware.publicPath.
   • quiet: Removed. This is now the default behavior for logging.
   • overlay: Moved to client.overlay.
   • before: Renamed to onBeforeSetupMiddleware. The function now receives the devServer instance, so you'd use devServer.app instead of the app argument.

Without these changes, the application's start script will break. This is a critical issue that needs to be addressed along with the version bump.