Http request which redirect to another hostname do not strip authorization header in @actions/http-client

Impact

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

The authorization header will get passed to the other domain.

Note that since this library is for actions, the GITHUB_TOKEN that is available in actions is generated and scoped per job with these permissions.

Patches

The problem is fixed in 1.0.8 at npm here. In 1.0.8, the authorization header is stripped before making the redirected request if the hostname is different.

Workarounds

None.

References

https://github.com/actions/http-client/pull/27

For more information

If you have any questions or comments about this advisory:

• Open an issue in https://github.com/actions/http-client/issues