Blackduck: Automated PR: Update typed-rest-client/1.7.3 to 1.8.11#269
Open
github-actions[bot] wants to merge 1 commit intoSIGINT-2349from
Open
Blackduck: Automated PR: Update typed-rest-client/1.7.3 to 1.8.11#269github-actions[bot] wants to merge 1 commit intoSIGINT-2349from
github-actions[bot] wants to merge 1 commit intoSIGINT-2349from
Conversation
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.
Vulnerabilities associated with typed-rest-client/1.7.3
CVE-2023-30846 (HIGH): typed-rest-client is a library for Node Rest and Http Clients with typings for use with TypeScript. Users of the typed-rest-client library version 1.7.3 or lower are vulnerable to leak authentication data to 3rd parties. The flow of the vulnerability is as follows: First, send any request with
BasicCredentialHandler,BearerCredentialHandlerorPersonalAccessTokenCredentialHandler. Second, the target host may return a redirection (3xx), with a link to a second host. Third, the next request will use the credentials to authenticate with the second host, by setting theAuthorizationheader. The expected behavior is that the next request will NOT set theAuthorizationheader. The problem was fixed in version 1.8.0. There are no known workarounds.Click Here To See More Details On Server