CVE-2022-24719 json
Unauthorized forwarding of confidential headers in fluture-node
published 2022-03-01 4 y ago modified 2026-07-20 3 mo ago also GHSA-32x6-qvw6-mxj4 , PYSEC-2022-43051 , PYSEC-2022-43052 , EUVD-2022-0215
- cvss
- 2.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm fluture-node 4.0.2
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.6 | CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.1 | 2.6 | CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | fluture-node | >=4.0.0, <4.0.2 |
4.0.2 |
Affected products
- fluture-js fluture-node
Classification
References
-
github.com
/psf/requests/pull/4718
web, patch, third-party-advisory
-
github.com
/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77
web, patch
-
github.com
/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4
web, patch
-
github.com
/fluture-js/fluture-node/security/advisories/GHSA-32x6-qvw6-mxj4
web, patch, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-24719
advisory
-
github.com
/fluture-js/fluture-node
package
-
github.com
/pypa/advisory-database/tree/main/vulns/pyquest/PYSEC-2022-43051.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/request-util/PYSEC-2022-43052.yaml
web
Sources
- CVE List CVE-2022-24719
- GitHub Advisory GHSA-32x6-qvw6-mxj4
- NVD CVE-2022-24719
- OSV PYSEC-2022-43052
- OSV PYSEC-2022-43051
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.