CVE-2022-0430: PYSEC-2022-167 - Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository httpie/httpie prior to 3.1.0.

CVE-2022-0430 · Severity: low · CVSS 3 · Published 2022-03-15

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

Technologies: httpie (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2022-0430 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2022-0430 being exploited in the wild.
How severe is CVE-2022-0430?
Low severity, with a CVSS score of 3, published 15 March 2022.
Which products and versions are affected?
httpie (PyPI) ECOSYSTEM:introduced=0,fixed=3.1.0, GIT:introduced=0,fixed=65ab7d5caaaf2f95e61f9dd65441801c2ddee38b|ECOSYSTEM:introduced=0,fixed=3.1.0.
Is there a fix for CVE-2022-0430?
Yes. httpie (PyPI): upgrade to 3.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2022-0430?
Check whether you run httpie (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • httpie (PyPI): upgrade to 3.1.0 or later
    pip install "httpie>=3.1.0"

Affected products

  • httpie (PyPI) ECOSYSTEM:introduced=0,fixed=3.1.0, GIT:introduced=0,fixed=65ab7d5caaaf2f95e61f9dd65441801c2ddee38b|ECOSYSTEM:introduced=0,fixed=3.1.0

Identifiers

  • CVE-2022-0430
  • GHSA-6pc9-xqrg-wfqw
  • PYSEC-2022-167

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.