microsoft/typed-rest-client · Security
Potential leak of authentication data to 3rd parties
- GHSA ID
- GHSA-558p-m34m-vpmq
- CVE ID
- CVE-2023-30846
- Severity
- critical
- Published
- Updated
- CVSS
- 9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- CVSS v3
- 9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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,BearerCredentialHandlerorPersonalAccessTokenCredentialHandler - 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
Authorizationheader.
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.
CWEs
- CWE-522 · Insufficiently Protected Credentials
References
- https://github.com/microsoft/typed-rest-client/security/advisories/GHSA-558p-m34m-vpmq ↗
- https://nvd.nist.gov/vuln/detail/CVE-2023-30846 ↗
- https://github.com/microsoft/typed-rest-client/pull/207 ↗
- https://github.com/microsoft/typed-rest-client/commit/f9ff755631b982ee1303dfc3e3c823d0d31233e8 ↗
- https://security.netapp.com/advisory/ntap-20230601-0008/ ↗
- https://github.com/advisories/GHSA-558p-m34m-vpmq ↗