Skip to content
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

Closed
grant-g opened this issue Apr 8, 2022 · 5 comments
Closed

new release of nconf needed to address CVE-2021-43138 #396

grant-g opened this issue Apr 8, 2022 · 5 comments

Comments

@grant-g
Copy link

grant-g commented Apr 8, 2022

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 in async 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!

@mhamann
Copy link
Collaborator

mhamann commented Apr 9, 2022

This should be possible, though there are breaking changes in async be that make it less than straightforward.

@grant-g
Copy link
Author

grant-g commented Apr 11, 2022

@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!

@mhamann
Copy link
Collaborator

mhamann commented Apr 12, 2022

The necessary changes have been merged into v0.x and will likely be released as v0.12 this week after some final testing.

@PaulAnnekov
Copy link

JFYI, nconf looks like not affected, because it's not using mapValues async method which is vulnerable according to CVE.

@mhamann
Copy link
Collaborator

mhamann commented Apr 15, 2022

Thanks for the insight, @PaulAnnekov.

v0.12.0 has been released to address the CVE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants