chore: upgrade follow-redirects from 1_5_10 to 1_16_0#5
Draft
00felix-app[bot] wants to merge 1 commit into
Draft
chore: upgrade follow-redirects from 1_5_10 to 1_16_0#500felix-app[bot] wants to merge 1 commit into
00felix-app[bot] wants to merge 1 commit into
Conversation
Open
This file contains hidden or 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
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 pull request upgrades the
follow-redirectsdependency from version 1.5.10 to 1.16.0 to address several critical security vulnerabilities. The update resolves issues that could lead to exposure of sensitive information, improper handling of URLs, and leakage of authentication headers across redirects.Vulnerabilities addressed:
url.parse().Proxy-Authorizationheader kept across hosts.No code changes are required; the dependency version update alone resolves these vulnerabilities. The upgrade is backward-compatible and ensures the module behaves correctly under redirect scenarios while protecting sensitive headers.