[Snyk] Fix for 1 vulnerabilities

[kingjay66]

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):

• docs/recipes/docker-server/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Denial of Service (DoS) SNYK-JS-WS-7266574	768

---

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:

🦉 Denial of Service (DoS)

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@lhci/cli@0.14.0	None	0	97.5 kB	hoten
npm/@lhci/server@0.14.0	network	0	23.5 MB	hoten
npm/@types/glob@7.2.0	None	0	6.61 kB	types
npm/glob@7.2.0	filesystem	0	54.7 kB	isaacs

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	CI
Filesystem access	npm/glob@7.2.0	Module: fs.realpath Location: Package overview	Source	🚫
Filesystem access	npm/glob@7.2.0	Module: fs Location: Package overview	Source	🚫
Filesystem access	npm/@storybook/core-common@6.5.13	Module: fs Location: Package overview	package.json	🚫
Dynamic require	npm/@storybook/core-common@6.5.13	Location: Package overview	package.json	🚫
Filesystem access	npm/@storybook/core-common@6.5.13	Module: fs-extra Location: Package overview	package.json	🚫
Dynamic require	npm/@storybook/core-common@6.5.13	Location: Package overview	package.json	🚫
Dynamic require	npm/@storybook/core-common@6.5.13	Location: Package overview	package.json	🚫
Dynamic require	npm/@storybook/core-common@6.5.13	Location: Package overview	package.json	🚫
Environment variable access	npm/@storybook/core-common@6.5.13	Env Vars: NODE_ENV Location: Package overview	package.json	🚫
Environment variable access	npm/@storybook/core-common@6.5.13	Env Vars: NODE_PATH Location: Package overview	package.json	🚫
Environment variable access	npm/@storybook/core-common@6.5.13	Env Vars: STORYBOOK Location: Package overview	package.json	🚫
Environment variable access	npm/@storybook/core-common@6.5.13	Env Vars: Location: Package overview	package.json	🚫
Environment variable access	npm/@storybook/core-common@6.5.13	Env Vars: name Location: Package overview	package.json	🚫
Filesystem access	npm/@storybook/core-common@6.5.13	Module: fs-extra Location: Package overview	package.json	🚫
Filesystem access	npm/@storybook/core-common@6.5.13	Module: fs Location: Package overview	package.json	🚫
Dynamic require	npm/@storybook/core-common@6.5.13	Location: Package overview	package.json	🚫
Dynamic require	npm/@storybook/core-common@6.5.13	Location: Package overview	package.json	🚫
Dynamic require	npm/@lhci/server@0.14.0	Location: Package overview	docs/recipes/docker-server/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 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 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.

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/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/glob@7.2.0
• @SocketSecurity ignore npm/@storybook/core-common@6.5.13
• @SocketSecurity ignore npm/@lhci/server@0.14.0