-
Notifications
You must be signed in to change notification settings - Fork 255
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
new release of nconf needed to address CVE-2021-43138 #396
Comments
This should be possible, though there are breaking changes in async be that make it less than straightforward. |
@mhamann Thank-you for looking into this. I'm sure this wasn't a task you had planned in the short-term, but there are likely many apps out there that need this update in order to stay compliant. If you run into blockers/delays please let us know here, thanks again! |
The necessary changes have been merged into |
JFYI, nconf looks like not affected, because it's not using |
Thanks for the insight, @PaulAnnekov. v0.12.0 has been released to address the CVE |
nconf release 0.11.3 has dependency
"async": "^1.4.0"
, which cannot satisfy CVE-2021-43138. A new release of nconf is needed that brings inasync 3.2.2
or newer.The guidance for apps that depend on packages like nconf is to resolve such findings within 15 days whenever possible. It would be very helpful if this can be resolved quickly, to give downstream apps an opportunity to adopt the fix in good time. Thank-you in advance!
The text was updated successfully, but these errors were encountered: