Direct Request ('Forced Browsing') Affecting python-treq package, versions *


Severity

Recommended
low

Based on Debian security rating.

Threat Intelligence

EPSS
0.24% (64th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN11-PYTHONTREQ-2394826
  • published5 Feb 2022
  • disclosed1 Feb 2022

Introduced: 1 Feb 2022

CVE-2022-23607  (opens in a new tab)
CWE-425  (opens in a new tab)

How to fix?

There is no fixed version for Debian:11 python-treq.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-treq package and not the python-treq package as distributed by Debian. See How to fix? for Debian:11 relevant fixed versions and status.

treq is an HTTP library inspired by requests but written on top of Twisted's Agents. Treq'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 ("supercookies"). 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.

CVSS Scores

version 3.1