Quick answers
- Is CVE-2022-0155 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-0155 being exploited in the wild.
- How severe is CVE-2022-0155?
- Low severity, with a CVSS score of 3, published 12 January 2022.
- Which products and versions are affected?
- follow-redirects (npm) SEMVER:introduced=0,fixed=1.14.7.
- Is there a fix for CVE-2022-0155?
- Yes. follow-redirects (npm): upgrade to 1.14.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-0155 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-0155?
- Check whether you run follow-redirects (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- follow-redirects (npm): upgrade to 1.14.7 or later
npm install follow-redirects@1.14.7
Technical details
follow-redirects is vulnerable to information disclosure (CWE-359) where sensitive HTTP headers, particularly authentication cookies, are transmitted across domain boundaries during redirect chains. The vulnerability occurs when the library automatically follows HTTP redirects without filtering security-sensitive headers before sending requests to different domains. An attacker can exploit this by crafting a redirect chain that originates from a legitimate domain and redirects to an attacker-controlled domain, causing the victim application to leak cookies and credentials. The fix, implemented in version 1.14.7, drops the Cookie header when following redirects across domain boundaries.
Affected products
- follow-redirects follow-redirects before 1.14.7
Identifiers
- CVE-2022-0155
- GHSA-74fj-2j2h-c42q
Timeline
- 2022-01-12: disclosed: Advisory published
- 2022-01-11: patched: Fix released in version 1.14.7