Skip to content

Potential leak of authentication data to 3rd parties

Critical severity GitHub Reviewed Published Apr 26, 2023 in microsoft/typed-rest-client • Updated Nov 12, 2023

Package

npm 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:

  1. Send any request with BasicCredentialHandler, BearerCredentialHandler or PersonalAccessTokenCredentialHandler
  2. The target host may return a redirection (3xx), with a link to a second host.
  3. 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:

  1. HTTP authentication leak in redirects - I used the same solution as CURL did.
  2. CVE-2018-1000007.

References

@mmrazik mmrazik published to microsoft/typed-rest-client Apr 26, 2023
Published by the National Vulnerability Database Apr 26, 2023
Published to the GitHub Advisory Database Apr 27, 2023
Reviewed Apr 27, 2023
Last updated Nov 12, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.326%
(72nd percentile)

Weaknesses

CVE ID

CVE-2023-30846

GHSA ID

GHSA-558p-m34m-vpmq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.