Typed Rest Client
Approved changes feed: RSS · Atom
cpe:2.3:a:microsoft:typed-rest-client:*:*:*:*:*:node.js:*:*
part: a version: * update: *
| Vendor | Microsoft (67206627-3ef6-5870-9d98-26a9f2e7065c) |
|---|---|
| Product | Typed Rest Client (6337406c-8dce-52bf-96d8-b55fa32049e7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | node.js |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-30846 |
vulnerable | 2026-06-08 06:04:41.205879 |
typed-rest-client vulnerable to potential leak of authentication data to 3rd parties
CRITICAL (9.1)
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`, `BearerCredentialHandler` or `PersonalAccessTokenCredentialHandler`. 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 the `Authorization` header. The expected behavior is that the next request will *NOT* set the `Authorization` header. The problem was fixed in version 1.8.0. There are no known workarounds.
Published: 2023-04-26T20:58:02.940Z
Updated: 2025-02-13T16:49:37.266Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.