-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Security Vulnerability: Prototype polution #1854
Comments
No plans to address that report, this project is not under active development. |
There is now a high severity CVE posted: Please consider fixing this. |
@d-haber, @peppertech, anyone else: if #1856 looks like a fix, then I can spin out a 2.3.7 version hopefully before next Monday. |
Thank you very much @jrburke really appreciate this update. |
I updated npm and the web site with 2.3.7. |
Merge the previous `denyProps` fix (3e9eb74) with `disallowedProps`, which apply to any call to `eachProps`.
Thank you @jrburke! |
Hello, @jrburke Can this please be considered for fixing as well? |
That one sounds like rephrasing of the same issue that was fixed in 2.3.7. If not, it would be good to have more specifics on how 2.3.7 has the problem. |
Thanks for taking a look. |
Are there any chances of getting a security fix that addresses this recently filed issue? https://security.snyk.io/vuln/SNYK-JS-REQUIREJS-5416713
There isn't a CVE posted for this yet, as it was just published last week. It is already showing up on multiple security scans however.
The text was updated successfully, but these errors were encountered: