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 dependency follow-redirects to v1.15.6 [SECURITY] #601
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/npm-follow-redirects-vulnerability
base: master
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
January 31, 2024 12:25
ecf8e86
to
972ddca
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
February 7, 2024 16:00
972ddca
to
bff30e6
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
February 26, 2024 15:31
bff30e6
to
0b295ac
Compare
renovate
bot
changed the title
Update dependency follow-redirects to v1.15.4 [SECURITY]
Update dependency follow-redirects to v1.15.6 [SECURITY]
Mar 16, 2024
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
March 16, 2024 20:21
0b295ac
to
1389954
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
March 19, 2024 11:17
1389954
to
bc4f177
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
March 25, 2024 22:29
bc4f177
to
fdd1aae
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
March 26, 2024 01:21
fdd1aae
to
dfec699
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
March 28, 2024 02:17
dfec699
to
192f4d8
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
April 3, 2024 15:02
192f4d8
to
ba392d0
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
2 times, most recently
from
April 9, 2024 23:44
cbe6438
to
b076308
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
2 times, most recently
from
April 25, 2024 10:26
ef5c030
to
ed2c790
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
April 25, 2024 23:34
ed2c790
to
e93b77b
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
April 29, 2024 12:49
e93b77b
to
b4c61f6
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
April 29, 2024 13:50
b4c61f6
to
61e4f14
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
April 30, 2024 10:11
61e4f14
to
af07bd9
Compare
renovate
bot
force-pushed
the
renovate/npm-follow-redirects-vulnerability
branch
from
April 30, 2024 17:08
af07bd9
to
327e3b1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
0 participants
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 PR contains the following updates:
1.15.5
->1.15.6
GitHub Vulnerability Alerts
CVE-2024-28849
When using axios, its dependency follow-redirects only clears authorization header during cross-domain redirect, but allows the proxy-authentication header which contains credentials too.
Steps To Reproduce & PoC
Test code:
When I meet the cross-domain redirect, the sensitive headers like authorization and cookie are cleared, but proxy-authentication header is kept.
Impact
This vulnerability may lead to credentials leak.
Recommendations
Remove proxy-authentication header during cross-domain redirect
Recommended Patch
follow-redirects/index.js:464
Release Notes
follow-redirects/follow-redirects (follow-redirects)
v1.15.6
Compare Source
Configuration
📅 Schedule: Branch creation - "" in timezone Europe/London, Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.