CVE-2022-24719: Fluture node Forwarding Of Confidentials Headers To Vulnerability
LOWCVE-2022-24719 is a LOW (CVSS 2.6) forwarding of confidentials headers to vulnerability (CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer) affecting Fluture node libraries in the npm ecosystem. The issue involves forwarding of confidentials headers to third parties in fluture-node. Remediation is available by upgrading affected packages to version 4.0.2.
CVE-2022-24719 at a Glance
Security Impact
CVSS: 2.6
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N).
How to Fix CVE-2022-24719
To remediate this vulnerability, upgrade all affected Fluture node dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install fluture-node@4.0.2Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls fluture-nodeHow to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2022-24719, inspect your project dependencies using npm:
npm ls fluture-nodeAnalyze the terminal output to locate any version of Fluture node in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.0.2), your application is affected.
Note: The npm ls fluture-node command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-212: Improper Removal of Sensitive Information Before Storage or Transfer, where the product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors. In Fluture node, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-24719 Affected Fluture node Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
fluture-node
|
npm |
≥ 4.0.0
< 4.0.2
|
4.0.2
|
References
Frequently Asked Questions
What is CVE-2022-24719?
Which Fluture node versions are affected?
What version fixes CVE-2022-24719?
Is fluture-node affected?
What is the CVSS score of CVE-2022-24719?
What CWE is associated with CVE-2022-24719?
How can I check npm dependencies for CVE-2022-24719?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-32x6-qvw6-mxj4",
"modified" : "2026-07-20T21:32:20Z",
"published" : "2022-03-01T22:14:57Z",
"aliases" : [ "CVE-2022-24719" ],
"summary" : "Forwarding of confidentials headers to third parties in fluture-node",
"details" : "### Impact\n\nUsing `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.\n\n### Patches\n\nThe redirection strategies made available in version 4.0.2 automatically redact confidential headers when a redirect is followed across to another origin.\n\n### Workarounds\n\nUse 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.\n\n### References\n\n- This vulnerability was discovered after the announcement of similar vulnerabilities in the `follow-redirects` package. There is more information there: https://github.com/advisories/GHSA-74fj-2j2h-c42q and https://huntr.dev/bounties/7cf2bf90-52da-4d59-8028-a73b132de0db/\n- Fixed in 125e4474f910c1507f8ec3232848626fbc0f55c4 and 0c99bc511533d48be17dc6bfe641f7d0aeb34d77",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N"
}, {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:A/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "fluture-node"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "4.0.2"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/fluture-js/fluture-node/security/advisories/GHSA-32x6-qvw6-mxj4"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-24719"
}, {
"type" : "WEB",
"url" : "https://github.com/psf/requests/pull/4718"
}, {
"type" : "WEB",
"url" : "https://github.com/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77"
}, {
"type" : "WEB",
"url" : "https://github.com/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/fluture-js/fluture-node"
}, {
"type" : "WEB",
"url" : "https://github.com/pypa/advisory-database/tree/main/vulns/pyquest/PYSEC-2022-43051.yaml"
}, {
"type" : "WEB",
"url" : "https://github.com/pypa/advisory-database/tree/main/vulns/request-util/PYSEC-2022-43052.yaml"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200", "CWE-212", "CWE-359", "CWE-601" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2022-03-01T22:14:57Z",
"nvd_published_at" : "2022-03-01T21:15:00Z"
}
}