socket-security[bot]
commented
3 months ago Report too large to display inline
Open renovate[bot] opened 3 months ago
socket-security[bot]
commented
3 months ago Report too large to display inline
socket-security[bot]
commented
3 months ago 🚨 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/nodemon@2.0.15 |
| 🚫 |
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 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.
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.
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/nodemon@2.0.15
This PR contains the following updates:
^3.1.0->^5.0.0GitHub 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-Originheader 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`](https://redirect.github.com/koajs/cors/blob/HEAD/History.md#500--2023-12-11) [Compare Source](https://redirect.github.com/koajs/cors/compare/4.0.0...5.0.0) \================== **others** - \[[`f31dac9`](http://github.com/koajs/cors/commit/f31dac99f5355c41e7d4dd3c4a80c5f154941a11)] - Merge pull request from GHSA-qxrj-hx23-xp82 (fengmk2 <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.
This PR was generated by Mend Renovate. View the repository job log.