human
Summarize this cyber threat intelligence report: Potential leak of authentication data to 3rd parties
Critical severity GitHub Reviewed Published 2 weeks ago in microsoft/typed-rest-client • Updated last week
Vulnerability details
Dependabot alerts
0
Package
 typed-rest-client (
npm
)
Affected versions
< 1.8.0
Patched versions
1.8.0
Description
Impact
Users of 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:

Send any request with BasicCredentialHandler, BearerCredentialHandler or PersonalAccessTokenCredentialHandler
The target host may return a redirection (3xx), with a link to a second host.
The next request will use the credentials to authenticate with the second host, by setting the Authorization header.
The expected behavior is that the next request will NOT set the Authorization header.

Patches
The problem was fixed on April 1st 2020.

Workarounds
There is no workaround.

References
This is similar to the following issues in nature:

HTTP authentication leak in redirects - I used the same solution as CURL did.
CVE-2018-1000007.
References
GHSA-558p-m34m-vpmq
https://nvd.nist.gov/vuln/detail/CVE-2023-30846
microsoft/typed-rest-client#207
microsoft/typed-rest-client@f9ff755
gpt
--- Reasoning ---
1. Is the question multiple-choice question?
No
2. Is it implied multiple-choice question?
No
3. If two experts were independently asked the question, will the final answer be exactly the same?
No

--- Answer ---
open