Quick answers
- Is CVE-2022-0536 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-0536 being exploited in the wild.
- How severe is CVE-2022-0536?
- Low severity, with a CVSS score of 3.1, published 10 February 2022.
- Which products and versions are affected?
- follow-redirects (npm) SEMVER:introduced=0,fixed=1.14.8.
- Is there a fix for CVE-2022-0536?
- Yes. follow-redirects (npm): upgrade to 1.14.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-0536 attacked?
- It is attacked over the network.
- Am I affected by CVE-2022-0536?
- 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.8 or later
npm install follow-redirects@1.14.8
Technical details
The vulnerability stems from improper header filtering when processing HTTP redirects across different URL schemes (e.g., HTTPS to HTTP). The library failed to drop sensitive headers (such as Authorization and Cookie headers) when following redirects, particularly across scheme boundaries where security downgrade is involved. An attacker can construct a malicious redirect chain that causes client applications using follow-redirects to inadvertently forward confidential credentials to attacker-controlled endpoints. The issue affects all versions prior to 1.14.8, which was patched to properly drop sensitive headers across schemes. The attack requires no authentication and is triggered by network-level HTTP redirect responses.
Affected products
- follow-redirects follow-redirects before 1.14.8
Identifiers
- CVE-2022-0536
- GHSA-pw2r-vq6v-hr8c
Timeline
- 2022-02-10: disclosed
- 2022-02-10: patched: fixed in version 1.14.8