fix(deps): update dependency @koa/cors to v5 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@koa/cors	^3.1.0 -> ^5.0.0

GitHub Vulnerability Alerts

CVE-2023-49803

Currently, the middleware operates in a way that if an allowed origin is not provided, it will return an Access-Control-Allow-Origin header with the value of the origin from the request. This behavior completely disables one of the most crucial elements of browsers - the Same Origin Policy (SOP), this could cause a very serious security threat to the users of this middleware.

If such behavior is expected, for instance, when middleware is used exclusively for prototypes and not for production applications, it should be heavily emphasized in the documentation along with an indication of the risks associated with such behavior, as many users may not be aware of it.

---

Release Notes

koajs/cors (@​koa/cors)

v5.0.0

Compare Source

==================

others

• [f31dac9] - Merge pull request from GHSA-qxrj-hx23-xp82 (fengmk2 <[email protected]>)

v4.0.0

Compare Source

==================

fixes

• [7358ab3] - fix: Calling all options even if origin header is not present (#​87) (Cleber Rossi <[email protected]>)

others

• [d19090f] - refactor: [BREAKING] drop node 8, 10, 12 support (#​88) (fengmk2 <<fengmk2@​gmail.com>>)

v3.4.3

Compare Source

==================

others

• [208b86c] - Revert "fix: Calling all options even if origin header is not present (#​87)" (fengmk2 <<fengmk2@​gmail.com>>)

v3.4.2

Compare Source

==================

fixes

• [2e8da5b] - fix: Calling all options even if origin header is not present (#​87) (Cleber Rossi <[email protected]>)

v3.4.1

Compare Source

==================

fixes

• [1205356] - fix: must specify an origin value instead of "*" wildcard (#​85) (Tyreal Hu <[email protected]>)

v3.4.0

Compare Source

==================

others

• [2cd4789] - 🤖 TEST: Run test on Node.js 18 (#​86) (fengmk2 <<fengmk2@​gmail.com>>)
• [ae56e05] - Create codeql-analysis.yml (fengmk2 <<fengmk2@​gmail.com>>)
• [c4b5d21] - refactor: use friendlier promise checking (#​84) (Swain Molster <[email protected]>)
• [fbe33bc] - 📖 DOC: Add privateNetworkAccess js to README (fengmk2 <<fengmk2@​gmail.com>>)

v3.3.0

Compare Source

==================

features

• [c279fc3] - feat: Add support for "Private Network Access" (#​83) (Chi Ma <[email protected]>)

others

• [97d9220] - chore: credentials jsdoc (#​80) (Jing Yi Wang <[email protected]>)

v3.2.0

Compare Source

==================

features

• [134ec9b] - feat: support secure context headers (Levi Tomes <[email protected]>)

others

• [bcadb55] - test: run test on github action (fengmk2 <<fengmk2@​gmail.com>>)

---

Configuration

📅 Schedule: Branch creation - "" in timezone Europe/Paris, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Report too large to display inline

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
Install scripts	npm/[email protected]	Install script: postinstall Source: node bin/postinstall || exit 0	api/package.json api/yarn.lock	🚫

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

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]