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

Arbitrary Code Execution Affecting thenify package, ALL versions #29

Closed
Rahul1408 opened this issue Jun 17, 2020 · 6 comments · Fixed by #30
Closed

Arbitrary Code Execution Affecting thenify package, ALL versions #29

Rahul1408 opened this issue Jun 17, 2020 · 6 comments · Fixed by #30

Comments

@Rahul1408
Copy link

Getting high severity vulnerability for thenify

Please check here: https://snyk.io/vuln/npm:thenify and provide the fixed version.

@dead-horse
Copy link
Member

Thanks for the reminder, it was fixed in 3.3.1

@Rahul1408
Copy link
Author

@dead-horse high severity vulnerability is still there in 3.3.1

https://snyk.io/vuln/npm:thenify

@rajivshah3
Copy link

@Rahul1408 I think Snyk just needs to update their DB. I'll contact their support team as I'm getting this alert as well

@AdamGold
Copy link

Hey! Adam from Snyk here. I've updated our database and you should expect to see the changes within the next hours :)

@Rahul1408
Copy link
Author

Rahul1408 commented Jun 18, 2020

Hey! Adam from Snyk here. I've updated our database and you should expect to see the changes within the next hours :)

thanks @AdamGold. Just FYI, High severity vulnerability is still showing in 3.3.1. Will take more time in DB sync?

@Rahul1408
Copy link
Author

Hey! Adam from Snyk here. I've updated our database and you should expect to see the changes within the next hours :)

thanks @AdamGold. Just FYI, High severity vulnerability is still showing in 3.3.1. Will take more time in DB sync.

it is fixed now with 3.3.1

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

Successfully merging a pull request may close this issue.

4 participants