Bump version of axios to fix CVE-2024-28849 #8
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I think we need to bump it to 1.7.5 as described here: #9 |
schalkwijk
force-pushed
the
bump-axios-version
branch
from
89596cd to
c3d7de9
Compare
This CVE is associated with `follow-redirects`, which is brought in by `axios`, so bumping `axios` to version 1.7.5 brings in the updated version of `follow-redirects` (1.15.6) without the vulnerability. This also resolves [another CVE here](groupdocs-conversion-cloud#9).
schalkwijk
force-pushed
the
bump-axios-version
branch
from
c3d7de9 to
0b22f36
Compare
|
@maiznadeem, the PR has been updated to bump axios to 1.7.5. Hopefully the maintainers approve! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This CVE is associated with
follow-redirects, which is brought in byaxios, so bumpingaxiosto version 1.7.5 brings in the updated version offollow-redirects(1.15.6) without the vulnerability. This also resolves another CVE here.