-
Notifications
You must be signed in to change notification settings - Fork 187
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
There is a vulnerability introduced by package axios #269
Comments
I will try to make a release this weekend |
Note there is another vulnerability (I can open another issue if necessary): CVE-2021-3749, which is only fixed in Unfortunately, this causes our app to break (I opened axios/axios#4099 to track the new issue). Basically, when making a call to Workaround would be for |
Update: |
Hey, can you raise a new issue. I will look over the weekend |
Opened #276 |
Hi, @skellock @rdewolff, there is a vulnerability introduced in your package apisauce:
Issue Description
A vulnerability CVE-2020-28168 detected in package axios<0.21.1 is directly referenced by [email protected]. We noticed that such a vulnerability has been removed since [email protected].
However, apisauce's popular previous version [email protected] (12,294 downloads per week) is still transitively referenced by a large amount of latest versions of active and popular downstream projects (about 168 downstream projects, e.g., amex-perks-sdk 2.1.3, @graphprotocol/indexer-cli 0.16.0, @kalutheo/uie 0.0.6, ontrac 2.1.8, sunubus-js-utils 1.1.11, [email protected], etc.).
As such, issue CVE-2020-28168 can be propagated into these downstream projects and expose security threats to them.
These projects cannot easily upgrade apisauce from version 1.1.2 to (>=2.0.0). For instance, [email protected] is introduced into the above projects via the following package dependency paths:
(1)
[email protected] ➔ [email protected] ➔ [email protected] ➔ [email protected]
......
The projects such as anticaptcha, which introduced [email protected], are not maintained anymore. These unmaintained packages can neither upgrade apisauce nor be easily migrated by the large amount of affected downstream projects.
On behalf the downstream users, could you help us remove the vulnerability from package [email protected]?
Suggested Solution
Since these inactive projects set a version constaint 1.1.* for apisauce on the above vulnerable dependency paths, if apisauce removes the vulnerability from 1.1.2 and releases a new patched version [email protected], such a vulnerability patch can be automatically propagated into the 168 affected downstream projects.
In [email protected], you can kindly try to perform the following upgrade:
axios ^0.19.0 ➔ ^0.21.1
;Note:
[email protected](>=0.21.1) has fixed the vulnerability (CVE-2020-28168)
Thank you for your contributions.
Best regards,
Paimon
The text was updated successfully, but these errors were encountered: