-
Notifications
You must be signed in to change notification settings - Fork 945
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
Update y18n to fix Prototype-Pollution (High) (CVE-2020-7774) #1102 #1106
Comments
@indexzero Do you think it would be possible to get this fixed? |
Ah, looks like you guys are really busy. Unfortunately this breaks our SCA scan for HIGH risk vulnerabilities so we are having to work off my forked repo :( |
I'll take a look today, sorry for the delay. |
@kibertoad thanks for the response. I'm here to help out in whatever way. |
@thenengah Problem with submitted PR is that it break compatibility with older (but still very widely used) Node versions. Considering that forever is a legacy software primarily used by legacy systems, this is not an ideal solution. |
@thenengah For |
@thenengah For |
^ PR to replace yargs with getopts I'm looking into configstore to replace nconf. Do you prefer one MR for both of these updates, or does it not matter? |
@thenengah Two PRs would be preferable! Thanks. |
@thenengah If configstore doesn't work out, there should be other alternatives. there is dotenv-json, but it wasn't updated in ages. There should be more. |
^ PR to replace nconf with configstore. |
@thenengah Merged getopts, left a comment for the |
Thank you! Will release new version today. |
@kibertoad 🔓 🏆 Thanks for your response time and help on this! Together we were able to remove the following vulnerability: |
@thenengah Thank you for your contributions! This is now released as 4.0.0 |
High risk security issue with nconf; just need to bump it
https://nodejs.org/en/blog/vulnerability/april-2021-security-releases/#npm-upgrade-update-y18n-to-fix-prototype-pollution-high-cve-2020-7774
#1105
The text was updated successfully, but these errors were encountered: