Exposure of Sensitive Information to an Unauthorized Actor in httpie
Impact
HTTPie have the practical concept of sessions, which help users to persistently store some of the state that belongs to the outgoing requests and incoming responses on the disk for further usage. As an example, we can make an authenticated request and save it to a named session called api:
$ http --session api -a user:pass pie.dev/basic-auth/user/pass{
"authenticated": true,
"user": "user"
}Since we have now saved the authentication data to that session, we won‘t have to enter it again and again on every invocation. We can simply reference the session, and HTTPie will use the saved state directly from it:
$ http --session api pie.dev/basic-auth/user/pass{
"authenticated": true,
"user": "user"
}One particular use case of these sessions is storing cookies (commonly referred to as a Cookie Jar). If a response has a Set-Cookie
header, HTTPie will parse it and store the actual cookie in the session. And from that point on, all outgoing requests will attach that cookie (in the form of a Cookie header).
This is extremely useful, especially when you are dealing with websites which manage their own state on the client-side through cookies.
$ http -F --session jar pie.dev/cookies/set/x/y{
"cookies": {
"x": "y"
}
}Before 3.1.0, HTTPie didn‘t distinguish between cookies and hosts they belonged. This behavior resulted in the exposure of some cookies when there are redirects originating from the actual host to a third party website, e.g:
$ http -F --session jar pie.dev/redirect-to url==https://httpbin.org/cookies(Pre 3.1.0)
{
"cookies": {
"x": "y"
}
}(Post 3.1.0)
{
"cookies": {}
}This behavior has been corrected in this release (with taking RFC 6265 — HTTP State Management Mechanism into the consideration).
A huge credit goes to @Glyph for disclosing the original vulnerability to us (through huntr.dev).
Patches
We suggest users to upgrade their HTTPie version to 3.1.0 or higher, and run httpie cli sessions upgrade command on their sessions.
For more information
If you have any questions or comments about this advisory:
- Email us:
security@httpie.io
Please note that this entry is covered by both CVE-2022-24737 and CVE-2022-0430.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Python (PyPI) | httpie | < 3.1.0 | 3.1.0 |
References
- https://github.com/httpie/httpie/commit/65ab7d5caaaf2f95e61f9dd65441801c2ddee38b
- https://github.com/httpie/httpie/releases/tag/3.1.0
- https://github.com/httpie/httpie/security/advisories/GHSA-9w4w-cpc8-h2fq
- https://nvd.nist.gov/vuln/detail/CVE-2022-24737
- https://github.com/httpie/httpie
- https://github.com/pypa/advisory-database/tree/main/vulns/httpie/PYSEC-2022-34.yaml
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4QZD2AZOL7XLNZVAV6GDNXYU6MFRU5RS
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/R5VYSYKEKVZEVEBIWAADGDXG4Y3EWCQ3
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/TXFCHGTW3V32GD6GXXJZE5QAOSDT3RTY
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N- Weakness (CWE)
CWE-200- Platform
- Python (PyPI)
- Package
httpie- Disclosed
- 07.03.2022
- Updated
- 11.10.2026 11:20
Sources and licenses
OSV / GitHub Advisory Database - PYSEC-2022-34 - PyPA Advisory Database; CC BY 4.0
OSV / GitHub Advisory Database - GHSA-9w4w-cpc8-h2fq - CC BY 4.0
Vulnerability history: httpie
All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 4
- First → latest
- 08.2019 11.2023
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 2
- Medium 2
Disclosures per year
- 2019: 1
- 2020: 0
- 2021: 0
- 2022: 2
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 0
-
Exposure of Sensitive Information to an Unauthorized Actor in httpie this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.