Skip to content
Fencer Intel
low 2.4

CVE-2022-0430 json

Exposure of Sensitive Information to an Unauthorized Actor in httpie/httpie

published 4y ago modified 4mo ago also GHSA-6pc9-xqrg-wfqw , PYSEC-2022-167 , EUVD-2022-0120

cvss
2.4
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository httpie/httpie prior to 3.1.0.

Patch / fix

  • pypi httpie 3.1.0
  • httpie httpie/httpie 3.1.0
  • httpie Debian 14, Debian 13, Debian 12 3.2.1-1

debian advisories DEBIAN-CVE-2022-0430

Is CVE-2022-0430 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-0430 updated cvss 5.3

httpie: Exposure of Sensitive Information to an Unauthorized Actor

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.29% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/dafb2e4f-c6b6-4768-8ef5-b396cd6a801f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 2.4 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.0 2.4 CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi httpie
<3.1.0
3.1.0

Affected products

  • httpie httpie/httpie

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.