| Package | Affected versions | Patched versions |
|---|---|---|
| pyquest | all versions | |
| request-util | all versions | |
| fluture-node | = 4.0.0= 4.0.1 | |
| fluture-node | ≥ 4.0.0, < 4.0.2 | 4.0.2 |
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.
Use a custom redirection strategy via the followRedirectsWith function. The custom strategy can be based on the new strategies available in [email protected].
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/Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free