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

Update "async": Security vulnerability, prototype pollution #408

Closed
klassm opened this issue Apr 13, 2022 · 14 comments
Closed

Update "async": Security vulnerability, prototype pollution #408

klassm opened this issue Apr 13, 2022 · 14 comments

Comments

@klassm
Copy link

klassm commented Apr 13, 2022

Hi there,

there is a security vulnerability in the old async version, which is currently in use (GHSA-fwr7-v2mv-hh25). Would id be possible to update async to the latest version? This is a jump however from 0.9.x to 3.x.

Thanks
Matthias

@huineng
Copy link

huineng commented Apr 13, 2022

https://github.ibm.com/advisories/GHSA-fwr7-v2mv-hh25
high severity
Vulnerable versions: < 3.2.2
Patched version: 3.2.2
A vulnerability exists in Async through 3.2.1 (fixed in 3.2.2) , which could let a malicious user obtain privileges via the mapValues() method.

@jacovinus
Copy link

fix waiting to be merged at #409

@nopeless
Copy link

subscribed so I can update ejs when its merged

@GoetzGoerisch
Copy link

Fixed with #411!
@mde can we get a new release please?

@jaishirole
Copy link

We too are waiting for the release with fix of #411 to be available.

@raejoonee
Copy link

Can't wait to upgrade to new release version with the fix of #411

@VamseeInala
Copy link

Waiting for the fix of #411 to be released

@JackHowa
Copy link
Contributor

Hopefully this will be released! #412 cc @mde

@shreya410
Copy link

Waiting for the async audit fix urgently, our production deployment is blocked because of this. Request to kindly expedite.

@alert-debug
Copy link

@shreya410 I share your sense of urgency, but I'm not sure that requesting that the work be expedited is what's needed here. Instead it's a good time to reflect on the fact that so many talented people are choosing to devote their time to produce this useful software and make it freely available to the world. It might be possible to expedite it if more people provided funding to support that development, though.

@shreya410
Copy link

Absolutely! I deeply appreciate everyone's contributions here. Apologies if this sounded ungrateful.

@mde
Copy link
Contributor

mde commented Apr 20, 2022

Apologies for the delay on this. Pushed to NPM, v10.8.5.

Re. funding, the the suggestions are appreciated, but I have a hard time imagining how donations for a project like this would pay anything resembling a full-time developer's salary.

Again, apologies for the delay pushing this out. I'll do my best to be a little more on top of these arbitrary bumps that are required to satisfy automated security audits.

And a quick reminder, I will delete posts on threads that I consider needlessly belligerent.

@mde mde closed this as completed Apr 20, 2022
@jakejs jakejs deleted a comment from VAchris Apr 20, 2022
@playground
Copy link

Same here,
Getting

async <2.6.4
Severity: high
Prototype Pollution in async - GHSA-fwr7-v2mv-hh25
fix available via npm audit fix --force
Will install prompt@0.1.7, which is a breaking change
node_modules/winston/node_modules/async
winston 0.4.0 - 3.0.0-rc6
Depends on vulnerable versions of async
node_modules/winston
prompt >=0.1.8
Depends on vulnerable versions of winston
node_modules/prompt

3 high severity vulnerabilities

@mde
Copy link
Contributor

mde commented Apr 25, 2022

This has been fixed. You need to update Jake.

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