ghsa-4qqq-9vqf-3h3f
Vulnerability from github
Published
2024-05-14 20:14
Modified
2024-05-20 20:22
Severity ?
Summary
Scrapy leaks the authorization header on same-domain but cross-origin redirects
Details
Impact
Since version 2.11.1, Scrapy drops the Authorization
header when a request is redirected to a different domain. However, it keeps the header if the domain remains the same but the scheme (http/https) or the port change, all scenarios where the header should also be dropped.
In the context of a man-in-the-middle attack, this could be used to get access to the value of that Authorization
header
Patches
Upgrade to Scrapy 2.11.2.
Workarounds
There is no easy workaround for unpatched versions of Scrapy. You can replace the built-in redirect middlewares with custom ones patched for this issue, but you have to patch them yourself, manually.
References
This security issue was reported and fixed by @szarny at https://huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a/.
{ "affected": [ { "package": { "ecosystem": "PyPI", "name": "Scrapy" }, "ranges": [ { "events": [ { "introduced": "0" }, { "fixed": "2.11.2" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-1968" ], "database_specific": { "cwe_ids": [ "CWE-200" ], "github_reviewed": true, "github_reviewed_at": "2024-05-14T20:14:33Z", "nvd_published_at": null, "severity": "MODERATE" }, "details": "### Impact\n\nSince version 2.11.1, Scrapy drops the `Authorization` header when a request is redirected to a different domain. However, it keeps the header if the domain remains the same but the scheme (http/https) or the port change, all scenarios where the header should also be dropped.\n\nIn the context of a man-in-the-middle attack, this could be used to get access to the value of that `Authorization` header\n\n### Patches\n\nUpgrade to Scrapy 2.11.2.\n\n### Workarounds\n\nThere is no easy workaround for unpatched versions of Scrapy. You can replace the built-in redirect middlewares with custom ones patched for this issue, but you have to patch them yourself, manually.\n\n### References\n\nThis security issue was reported and fixed by @szarny at https://huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a/.\n", "id": "GHSA-4qqq-9vqf-3h3f", "modified": "2024-05-20T20:22:55Z", "published": "2024-05-14T20:14:33Z", "references": [ { "type": "WEB", "url": "https://github.com/scrapy/scrapy/security/advisories/GHSA-4qqq-9vqf-3h3f" }, { "type": "WEB", "url": "https://github.com/scrapy/scrapy/commit/1d0502f25bbe55a22899af915623fda1aaeb9dd8" }, { "type": "PACKAGE", "url": "https://github.com/scrapy/scrapy" }, { "type": "WEB", "url": "https://huntr.com/bounties/27f6a021-a891-446a-ada5-0226d619dd1a" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", "type": "CVSS_V3" } ], "summary": "Scrapy leaks the authorization header on same-domain but cross-origin redirects" }
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.