Information Disclosure in @actions/http-client (CVE-2020-11021)
Summary
Vulnerability in @actions/http-client (CVE-2020-11021). Confidential information can be exposed externally. Exploitable via Authorization header. Mitigation: upgrade to 1.0.8 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2020-11021 has been found in @actions/http-client.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade @actions/http-client to 1.0.8 or later.
If unsure, ask your IT team or search "@actions/http-client CVE-2020-11021" on the vendor's site.
CVE-2020-11021 (@actions/http-client) — CWE-200
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header
Patched: 1.0.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in @actions/http-client. Attackers reach the vulnerable code path via Authorization header without authentication.
Check the vendor advisory for the affected versions of @actions/http-client. Attack surface: Authorization header.
Severity: ?. Confidential information can be exposed externally.
Update to 1.0.8.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@actions/http-client' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@actions/http-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@actions/http-clientを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @actions/http-client to 1.0.8ステージング環境で 1.0.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- web github.com