CVE-2020-11021 HTTP request which redirect to another hostname do not strip authorization header in Actions Http-Client
Attackers can steal authorization headers when HTTP requests redirect to a different domain, exposing sensitive credentials to unintended hosts.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2020-11021?
CVE-2020-11021 is a medium-severity vulnerability in actions http-client, published on 29 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-200
Which versions are affected by CVE-2020-11021?
2 open source packages ship an affected version, including @actions/http-client. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
@actions/http-client npm | All versions | 1.0.8 |
@actions/http-client npm | All versions | 1.0.8 |
Products include Http-Client Project Http-Client.
How do I fix CVE-2020-11021?
Upgrade @actions/http-client to 1.0.8 or later.
Is CVE-2020-11021 being exploited?
There is no known exploitation of CVE-2020-11021 in the wild and no public exploit code.
Sources
Also known as GHSA-9w6v-m7wp-jwg4.