https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 23:52:33 +0000 https://cve.radiocsirt.org/vuln/cve-2022-23607 <p><strong>Affected:</strong> twisted treq</p> <p>treq is an HTTP library inspired by requests but written on top of Twisted&#39;s Agents. Treq&#39;s request methods (`treq.get`, `treq.post`, etc.) and `treq.client.HTTPClient` constructor accept cookies as a dictionary. Such cookies are not bound to a single domain, and are therefore sent to *every* domain (&#34;supercookies&#34;). This can potentially cause sensitive information to leak upon an HTTP redirect to a different domain., e.g. should `https://example.com` redirect to `http://cloudstorageprovider.com` the latter will receive the cookie `session`. Treq 2021.1.0 and later bind cookies given to request methods (`treq.request`, `treq.get`, `HTTPClient.request`, `HTTPClient.get`, etc.) to the origin of the *url* parameter. Users are advised to upgrade. For users unable to upgrade Instead of passing a dictionary as the *cookies* argument, pass a `http.cookiejar.CookieJar` instance with properly domain- and scheme-scoped cookies in it.</p> <p><strong>Affected:</strong> twisted treq</p> <p>treq is an HTTP library inspired by requests but written on top of Twisted&#39;s Agents. Treq&#39;s request methods (`treq.get`, `treq.post`, etc.) and `treq.client.HTTPClient` constructor accept cookies as a dictionary. Such cookies are not bound to a single domain, and are therefore sent to *every* domain (&#34;supercookies&#34;). This can potentially cause sensitive information to leak upon an HTTP redirect to a different domain., e.g. should `https://example.com` redirect to `http://cloudstorageprovider.com` the latter will receive the cookie `session`. Treq 2021.1.0 and later bind cookies given to request methods (`treq.request`, `treq.get`, `HTTPClient.request`, `HTTPClient.get`, etc.) to the origin of the *url* parameter. Users are advised to upgrade. For users unable to upgrade Instead of passing a dictionary as the *cookies* argument, pass a `http.cookiejar.CookieJar` instance with properly domain- and scheme-scoped cookies in it.</p> https://cve.radiocsirt.org/vuln/cve-2022-23607 https://cve.radiocsirt.org/vuln/ghsa-fhpf-pp6p-55qc <p><strong>Affected:</strong> PyPI: treq</p> <p>### Impact</p> <p>Treq&#39;s request methods (`treq.get`, `treq.post`, `HTTPClient.request`, `HTTPClient.get`, etc.) accept cookies as a dictionary, for example:</p> <p>```py treq.get(&#39;https://example.com/&#39;, cookies={&#39;session&#39;: &#39;1234&#39;}) ```</p> <p>Such cookies are not bound to a single domain, and are therefore sent to *every* domain (&#34;supercookies&#34;). This can potentially cause sensitive information to leak upon an HTTP redirect to a different domain., e.g. should `https://example.com` redirect to `http://cloudstorageprovider.com` the latter will receive the cookie `session`.</p> <p>### Patches</p> <p>Treq 2021.1.0 and later bind cookies given to request methods (`treq.request`, `treq.get`, `HTTPClient.request`, `HTTPClient.get`, etc.) to the origin of the *url* parameter.</p> <p>### Workarounds</p> <p>Instead of passing a dictionary as the *cookies* argument, pass a `http.cookiejar.CookieJar` instance with properly domain- and scheme-scoped cookies in it:</p> <p>```py from http.cookiejar import CookieJar from requests.cookies import create_cookie</p> <p>jar = CookieJar() jar.add_cookie( create_cookie( name=&#39;session&#39;, value=&#39;1234&#39;, domain=&#39;example.com&#39;, secure=True, ), ) client = HTTPClient(cookies=jar) client.get(&#39;https://example.com/&#39;) ```</p> <p>### References</p> <p>* Originally reported at [huntr.dev](https://huntr.dev/bounties/3c9204fc-a3d1-4441-8599-924c5f57e7ae/?token=06d930e37046c914bcb037e85cc227dc7b510b475989fc69837566562ba899277d46b0fb4b1e21cdcb6ddc1b7d9b1ded632cf3a3551ecb89afca16a63b34641284…</p> <p><strong>Affected:</strong> PyPI: treq</p> <p>### Impact</p> <p>Treq&#39;s request methods (`treq.get`, `treq.post`, `HTTPClient.request`, `HTTPClient.get`, etc.) accept cookies as a dictionary, for example:</p> <p>```py treq.get(&#39;https://example.com/&#39;, cookies={&#39;session&#39;: &#39;1234&#39;}) ```</p> <p>Such cookies are not bound to a single domain, and are therefore sent to *every* domain (&#34;supercookies&#34;). This can potentially cause sensitive information to leak upon an HTTP redirect to a different domain., e.g. should `https://example.com` redirect to `http://cloudstorageprovider.com` the latter will receive the cookie `session`.</p> <p>### Patches</p> <p>Treq 2021.1.0 and later bind cookies given to request methods (`treq.request`, `treq.get`, `HTTPClient.request`, `HTTPClient.get`, etc.) to the origin of the *url* parameter.</p> <p>### Workarounds</p> <p>Instead of passing a dictionary as the *cookies* argument, pass a `http.cookiejar.CookieJar` instance with properly domain- and scheme-scoped cookies in it:</p> <p>```py from http.cookiejar import CookieJar from requests.cookies import create_cookie</p> <p>jar = CookieJar() jar.add_cookie( create_cookie( name=&#39;session&#39;, value=&#39;1234&#39;, domain=&#39;example.com&#39;, secure=True, ), ) client = HTTPClient(cookies=jar) client.get(&#39;https://example.com/&#39;) ```</p> <p>### References</p> <p>* Originally reported at [huntr.dev](https://huntr.dev/bounties/3c9204fc-a3d1-4441-8599-924c5f57e7ae/?token=06d930e37046c914bcb037e85cc227dc7b510b475989fc69837566562ba899277d46b0fb4b1e21cdcb6ddc1b7d9b1ded632cf3a3551ecb89afca16a63b34641284…</p> https://cve.radiocsirt.org/vuln/ghsa-fhpf-pp6p-55qc