[Snyk] Security upgrade webpack-dev-server from 3.11.3 to 4.0.0

[naiba4]

This PR was automatically created by Snyk using the credentials of a real user.


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

Snyk changed the following file(s):

• demo/webpack/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Server-Side Request Forgery (SSRF) SNYK-JS-IP-7148531	718

---

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)

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	environment, eval, network Transitive: filesystem	+22	1.76 MB	evilebottnawi

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	demo/webpack/package.json
Debug access	npm/[email protected]	Module: module Location: Package overview	orphan: npm/[email protected]
Unmaintained	npm/[email protected]	Last Publish: 4/9/2018, 9:49:47 AM	orphan: npm/[email protected]
Trivial Package	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	demo/webpack/package.json
Trivial Package	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Trivial Package	npm/[email protected]	Location: Package overview	orphan: npm/[email protected]
Unmaintained	npm/[email protected]	Last Publish: 4/30/2019, 12:53:23 PM	demo/webpack/package.json
Trivial Package	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Deprecated	npm/[email protected]	Reason: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!	demo/webpack/package.json
Unmaintained	npm/[email protected]	Last Publish: 10/15/2017, 1:12:51 PM	demo/webpack/package.json
Unmaintained	npm/[email protected]	Last Publish: 10/13/2017, 12:48:00 AM	demo/webpack/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	demo/webpack/package.json
Unmaintained	npm/[email protected]	Last Publish: 10/15/2017, 1:12:46 PM	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: NODE_ENV Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: BABEL_ENV Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: BABEL_CACHE_PATH Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: BABEL_DISABLE_CACHE Location: Package overview	demo/webpack/package.json
Shell access	npm/[email protected]	Module: child_process Location: Package overview	demo/webpack/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: EDITOR Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: VISUAL Location: Package overview	demo/webpack/package.json
Uses eval	npm/[email protected]	Eval Type: Function Location: Package overview	demo/webpack/package.json
Unmaintained	npm/[email protected]	Last Publish: 10/15/2017, 1:11:55 PM	demo/webpack/package.json
Deprecated	npm/[email protected]	Reason: Package no longer supported. Contact [email protected] for more info.	demo/webpack/package.json
Unmaintained	npm/[email protected]	Last Publish: 11/7/2014, 6:17:52 PM	demo/webpack/package.json
Unmaintained	npm/[email protected]	Last Publish: 10/15/2017, 1:13:00 PM	demo/webpack/package.json
Unmaintained	npm/[email protected]	Last Publish: 5/30/2017, 11:07:09 AM	demo/webpack/package.json
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Filesystem access	npm/[email protected]	Module: fs Location: Package overview	demo/webpack/package.json
Minified code	npm/[email protected]	Confidence: 1.00 Location: Package overview	demo/webpack/package.json
Uses eval	npm/[email protected]	Eval Type: Function Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: WEBPACK_DEV_SERVER_PORT_RETRY Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: WEBPACK_DEV_SERVER_BASE_PORT Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: WEBPACK_SERVE Location: Package overview	demo/webpack/package.json
Network access	npm/[email protected]	Module: net Location: Package overview	demo/webpack/package.json
Network access	npm/[email protected]	Module: globalThis["fetch"] Location: Package overview	demo/webpack/package.json
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Network access	npm/[email protected]	Module: http-proxy-middleware Location: Package overview	demo/webpack/package.json
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Dynamic require	npm/[email protected]	Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: WS_NO_BUFFER_UTIL Location: Package overview	demo/webpack/package.json
Environment variable access	npm/[email protected]	Env Vars: WS_NO_UTF_8_VALIDATE Location: Package overview	demo/webpack/package.json
Network access	npm/[email protected]	Module: http Location: Package overview	demo/webpack/package.json
Network access	npm/[email protected]	Module: https Location: Package overview	demo/webpack/package.json
Network access	npm/[email protected]	Module: net Location: Package overview	demo/webpack/package.json
Network access	npm/[email protected]	Module: tls Location: Package overview	demo/webpack/package.json

View full report↗︎

Next steps

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is debug access?

Uses debug, reflection and dynamic code execution features.

Removing the use of debug will reduce the risk of any reflection and dynamic code execution.

What are unmaintained packages?

Package has not been updated in more than 5 years and may be unmaintained. Problems with the package may go unaddressed.

Package should publish periodic maintenance releases if they are maintained, or deprecate if they have no intention in further maintenance.

What are trivial packages?

Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency.

Removing this package as a dependency and implementing its logic will reduce supply chain risk.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is shell access?

This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code.

Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced.

What is eval?

Package uses eval() which is a dangerous function. This prevents the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use eval, since this could potentially execute any code.

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

What's wrong with minified code?

This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code.

In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm.

What is network access?

This module accesses the network.

Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud