CVE-2022-24719: Forwarding of confidentials headers to third parties in fluture-node
(updated )
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.
References
- github.com/advisories/GHSA-32x6-qvw6-mxj4
- github.com/fluture-js/fluture-node/commit/0c99bc511533d48be17dc6bfe641f7d0aeb34d77
- github.com/fluture-js/fluture-node/commit/125e4474f910c1507f8ec3232848626fbc0f55c4
- github.com/fluture-js/fluture-node/security/advisories/GHSA-32x6-qvw6-mxj4
- github.com/psf/requests/pull/4718
- github.com/pypa/advisory-database/tree/main/vulns/pyquest/PYSEC-2022-43051.yaml
- github.com/pypa/advisory-database/tree/main/vulns/request-util/PYSEC-2022-43052.yaml
- nvd.nist.gov/vuln/detail/CVE-2022-24719
Code Behaviors & Features
Detect and mitigate CVE-2022-24719 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →