[Snyk] Security upgrade express from 4.18.1 to 4.21.1

[Hawthorne001]

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

Snyk changed the following file(s):

• iam/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:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-JS-COOKIE-8163060	44

---

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:

🦉 Cross-site Scripting (XSS)

[socket-security]

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

Package	New capabilities	Transitives	Size	Publisher
npm/@chakra-ui/[email protected]	None	+15	5.08 MB	segunadebayo
npm/@datadog/[email protected]	Transitive: network	+1	1.27 MB	datadog
npm/@datadog/[email protected]	Transitive: network	+2	3.04 MB	datadog
npm/@didtools/[email protected]	None	+4	262 kB	dav1do
npm/@didtools/[email protected]	None	+7	2.72 MB	dbcfd
npm/@emotion/[email protected]	Transitive: environment, filesystem	+34	9.63 MB	emotion-release-bot
npm/@emotion/[email protected]	Transitive: environment, filesystem	+32	8.82 MB	emotion-release-bot
npm/@ethereum-attestation-service/[email protected]	Transitive: filesystem, network	+37	20.6 MB	lbeder
npm/@ethersproject/[email protected]	network	+24	2.96 MB	ricmoo
npm/@headlessui/[email protected]	environment	+3	815 kB	malfaitrobin
npm/@headlessui/[email protected]	environment	0	10.3 kB	malfaitrobin
npm/@heroicons/[email protected]	None	0	3.69 MB	malfaitrobin
npm/@next/[email protected]	filesystem	0	46.6 kB	vercel-release-bot
npm/@popperjs/[email protected]	None	0	1.46 MB	fezvrasta
npm/@self.id/[email protected]	Transitive: environment, eval, filesystem, network, shell	+170	40.7 MB	zachferland
npm/@testing-library/[email protected]	None	+8	990 kB	testing-library-bot
npm/@testing-library/[email protected]	environment	+19	9.59 MB	testing-library-bot
npm/@testing-library/[email protected]	Transitive: environment	+19	4.59 MB	testing-library-bot
npm/@types/[email protected]	None	0	71.4 kB	types
npm/@types/[email protected]	None	0	0 B
npm/@types/[email protected]	None	0	4.42 kB	types
npm/@types/[email protected]	None	+2	1.69 MB	types
npm/@typescript-eslint/[email protected]	Transitive: environment	+11	5.31 MB	jameshenry
npm/@typescript-eslint/[email protected]	Transitive: environment	+5	1.42 MB	jameshenry
npm/@web3-onboard/[email protected]	Transitive: environment, network	+51	36 MB	cmeisl
npm/@web3-onboard/[email protected]	Transitive: environment, network	+11	18.2 MB	cmeisl
npm/@web3-onboard/[email protected]	Transitive: environment, network	+11	17.8 MB	cmeisl
npm/@web3-onboard/[email protected]	Transitive: environment, filesystem, network	+117	53.4 MB	cmeisl
npm/@web3-onboard/[email protected]	Transitive: environment, network	+11	17.8 MB	cmeisl
npm/[email protected]	environment Transitive: filesystem	+3	2.52 MB	ai
npm/[email protected]	environment Transitive: eval, filesystem, shell	+70	14.1 MB	simenb
npm/[email protected]	filesystem, network	+2	753 kB	pubkey
npm/[email protected]	None	0	414 kB	lpinca
npm/[email protected]	None	+14	3.63 MB	ukstv
npm/[email protected]	None	+14	3.63 MB	paul_lecam
npm/[email protected]	unsafe Transitive: environment, filesystem	+40	9.57 MB	vercel-release-bot
npm/[email protected]	None	0	20.8 kB	lydell
npm/[email protected]	filesystem Transitive: environment	+9	2.72 MB	simenb
npm/[email protected]	environment, filesystem Transitive: eval, unsafe	+24	7.56 MB	eslintbot

🚮 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	CI
Critical CVE	npm/[email protected]	CVE: GHSA-mpj8-q39x-wq5h crypto-es PBKDF2 1,000 times weaker than specified in 1993 and 1.3M times weaker than current standard (CRITICAL) Affected versions: < 2.1.0 Patched version: 2.1.0	app/package.json	⚠︎
Protestware or potentially unwanted behavior	npm/[email protected]	Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts.	Source	⚠︎
Protestware or potentially unwanted behavior	npm/[email protected]	Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale	Source	⚠︎

View full report↗︎

Next steps

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is protestware?

This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function.

Consider that consuming this package may come along with functionality unrelated to its primary purpose.

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]