Http Client
Approved changes feed: RSS · Atom
cpe:2.3:a:http-client_project:http-client:*:*:*:*:*:node.js:*:*part: a version: * update: *
| Vendor | Http Client Project (6aeb28c1-3dbf-5a38-9650-b59546ea11d6) |
|---|---|
| Product | Http Client (12f27c98-ed9a-5328-b52c-ba26a93f5b95) |
| 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-2020-11021 |
vulnerable | 2026-06-08 05:16:36.223388 |
HTTP request which redirect to another hostname do not strip authorization header in Actions Http-Client
MEDIUM (6.3)
Actions Http-Client (NPM @actions/http-client) before version 1.0.8 can disclose Authorization headers to incorrect domain in certain redirect scenarios. The conditions in which this happens are if consumers of the http-client: 1. make an http request with an authorization header 2. that request leads to a redirect (302) and 3. the redirect url redirects to another domain or hostname Then the authorization header will get passed to the other domain. The problem is fixed in version 1.0.8.
Published: 2020-04-29T18:00:20.000Z
Updated: 2024-08-04T11:21:14.534Z |
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.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.