CVE-2022-24737 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in httpie. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for httpie — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in httpie
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2022-24737.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
httpieReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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:
[email protected]
Please note that this entry is covered by both CVE-2022-24737 and CVE-2022-0430.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | httpie | all versions | 3.1.0pip install --upgrade 'httpie==3.1.0' |
Affected Products
fedorafedoraprojecthttpiehttpieResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for httpie, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update httpie to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24737 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2022-24737 in your dependencies?
Find it across PyPI, including transitive dependencies.