[Snyk] Security upgrade express from 4.17.1 to 4.19.2

[kingjay66]

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

Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • packages/cli/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning

Failed to update the yarn.lock, please update manually before merging.

Vulnerabilities that will be fixed

With an upgrade:

Severity	Priority Score (*)	Issue	Breaking Change	Exploit Maturity
	591/1000 Why? Recently disclosed, Has a fix available, CVSS 6.1	Open Redirect SNYK-JS-EXPRESS-6474509	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Check the changes in this PR to ensure they won't cause issues with your project.

---

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

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Open Redirect

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@webassemblyjs/floating-point-hex-parser@1.9.0	None	0	6.37 kB	xtuc
npm/@webassemblyjs/helper-api-error@1.9.0	None	0	6.1 kB	xtuc
npm/@webassemblyjs/helper-buffer@1.9.0	None	0	8.7 kB	xtuc
npm/@webassemblyjs/helper-wasm-bytecode@1.9.0	None	0	24.2 kB	xtuc
npm/@webassemblyjs/utf8@1.9.0	None	0	11.2 kB	xtuc
npm/diff-sequences@26.6.2	None	0	52.7 kB	simenb
npm/fast-levenshtein@2.0.6	None	0	9.44 kB	hiddentao
npm/tapable@1.1.3	None	0	40.6 kB	sokra
npm/yargs-parser@20.2.9	environment, filesystem	0	124 kB	oss-bot

🚮 Removed packages: npm/entities@1.1.2, npm/is-alphabetical@1.0.4, npm/json-stringify-safe@5.0.1, npm/lodash.uniq@4.5.0, npm/mute-stream@0.0.7, npm/os-tmpdir@1.0.2, npm/statuses@1.5.0, npm/through@2.3.8

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/require-directory@2.1.1	Module: fs Location: Package overview	orphan: npm/require-directory@2.1.1
Shell access	npm/detect-libc@1.0.3	Module: child_process Location: Package overview	orphan: npm/detect-libc@1.0.3
Filesystem access	npm/detect-libc@1.0.3	Module: fs Location: Package overview	orphan: npm/detect-libc@1.0.3
Environment variable access	npm/detect-libc@1.0.3	Env Vars: Location: Package overview	orphan: npm/detect-libc@1.0.3
Filesystem access	npm/yargs-parser@20.2.9	Module: fs Location: Package overview	Source
Environment variable access	npm/yargs-parser@20.2.9	Env Vars: Location: Package overview	Source
Environment variable access	npm/yargs-parser@20.2.9	Env Vars: YARGS_MIN_NODE_VERSION Location: Package overview	Source
Dynamic require	npm/yargs-parser@20.2.9	Location: Package overview	Source
New author	npm/domain-browser@1.2.0	New Author: bevryme Previous Author: balupton	orphan: npm/domain-browser@1.2.0
Network access	npm/get-port@4.2.0	Module: net Location: Package overview	orphan: npm/get-port@4.2.0

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 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 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 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 new author?

A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.

Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights.

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

• @SocketSecurity ignore npm/require-directory@2.1.1
• @SocketSecurity ignore npm/detect-libc@1.0.3
• @SocketSecurity ignore npm/yargs-parser@20.2.9
• @SocketSecurity ignore npm/domain-browser@1.2.0
• @SocketSecurity ignore npm/get-port@4.2.0