What’s Vulnerable › Vulnerabilities
CVE-2022-24719: Unauthorized forwarding of confidential headers in fluture-node
- Severity: medium (CVSS 6.1 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.8% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2022-03-01 · updated 2026-06-17
- Weakness: CWE-359
Description
Fluture-Node is a FP-style HTTP and streaming utils for Node based on Fluture. Using `followRedirects` or `followRedirectsWith` with any of the redirection strategies built into fluture-node 4.0.0 or 4.0.1, paired with a request that includes confidential headers such as Authorization or Cookie, exposes you to a vulnerability where, if the destination server were to redirect the request to a server on a third-party domain, or the same domain over unencrypted HTTP, the headers would be included in the follow-up request and be exposed to the third party, or potential http traffic sniffing. The redirection strategies made available in version 4.0.2 automatically redact confidential headers when a redirect is followed across to another origin. A workaround has been identified by using a custom redirection strategy via the `followRedirectsWith` function. The custom strategy can be based on the new strategies available in fluture-node@4.0.2.
Affected products
- fluture-js fluture-node: 4.0.0, 4.0.1
References
- https://github.com/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77
- https://github.com/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4
- https://github.com/fluture-js/fluture-node/security/advisories/GHSA-32x6-qvw6-mxj4
- https://github.com/psf/requests/pull/4718
- https://github.com/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77
- https://github.com/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4
- https://github.com/fluture-js/fluture-node/security/advisories/GHSA-32x6-qvw6-mxj4
- https://github.com/psf/requests/pull/4718
Get alerted when CVE-2022-24719 or the next vulnerability affects your stack