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.
Remediation
References
https://github.com/actions/http-client/commit/f6aae3dda4f4c9dc0b49737b36007330f78fd53a
https://github.com/actions/http-client/security/advisories/GHSA-9w6v-m7wp-jwg4
https://github.com/actions/http-client/pull/27
Related Vulnerabilities
CVE-2023-26149 Vulnerability in maven package org.webjars.npm:quill-mention
CVE-2021-23380 Vulnerability in npm package roar-pidusage
CVE-2020-21125 Vulnerability in maven package com.bstek.ureport:ureport2-console
CVE-2022-31151 Vulnerability in npm package undici
CVE-2021-25122 Vulnerability in maven package org.apache.tomcat.embed:tomcat-embed-core