Debian LinuxOperating system · Debian
CVE-2022-23607
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedtreq 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencetreq HTTP library accepted cookies as a dictionary, which were not bound to any specific domain. These 'supercookies' were sent to every domain the client contacted. When a redirect occurred from one domain to another (e.g., example.com to cloudstorageprovider.com), sensitive cookie data like session identifiers would leak to the redirect target.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 9.0>= 21.1.0, < 22.1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify treq installation and versionRun 'pip show treq' or check your requirements file for the installed treq version. Compare against the affected range: >= 21.1.0, < 22.1.0Affected if The installed treq version falls within 21.1.0 through 21.x.x (prior to 22.1.0)
-
Locate code using treq with cookie parametersSearch your codebase for treq API calls that pass cookies, such as treq.get(), treq.post(), or treq.request() with a 'cookies' keyword argumentAffected if Code passes cookies as a dictionary to any treq request method
-
Inspect cookie parameter typeExamine the cookies parameter being passed - look for patterns like cookies={'session': 'xyz'} which indicates dictionary-based (unbounded) cookies versus cookies=jar where jar is a http.cookiejar.CookieJarAffected if Cookies are passed as a plain dictionary (e.g., cookies={'key': 'value'}) rather than a CookieJar object
-
Determine if redirects are followedCheck if your treq requests explicitly or implicitly follow redirects (default behavior), and whether cross-domain redirects could occur between different domains in your application workflowAffected if Your application follows redirects and makes requests that could redirect from one domain to another (e.g., example.com to a third-party service)
-
Assess data sensitivity in redirect scenariosReview which endpoints use dictionary cookies and could experience cross-domain redirects, exposing session tokens or authentication credentials to redirect target domainsAffected if Sensitive authentication cookies (session IDs, tokens) are sent via treq dictionary cookies to endpoints that may redirect to different domains
You are affected if you use treq version 21.1.0 through 21.x.x and pass cookies as a dictionary to requests that may follow redirects across different domains.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped22.1.0
Upgrade to treq 2021.1.0 or later where cookies are bound to the origin of the request URL. Alternatively, replace dictionary-based cookies with http.cookiejar.CookieJar instances containing properly domain-scoped cookies.
treq >= 22.1.0
- Update the treq package to version 22.1.0 or later using your Python package manager (e.g., pip install treq>=22.1.0)
- After upgrading, verify that your code uses the updated library version by checking treq.__version__
- Test your application to ensure cookie handling works as expected with the new version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23607 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data