# CVE-2022-31043: Fix failure to strip Authorization header on HTTP downgrade in Guzzle

> Attackers can intercept sensitive Authorization headers when Guzzle clients follow redirects from HTTPS to HTTP, exposing credentials.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2022
- **Updated:** 23 Apr 2025
- **Also known as:** CLSA-2026-1783645385, DEBIAN-CVE-2022-31043, UBUNTU-CVE-2022-31043

## What is CVE-2022-31043?

CVE-2022-31043 is a high-severity vulnerability in Debian Debian Linux, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Guzzle is an open source PHP HTTP client. In affected versions `Authorization` headers on requests are sensitive information. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, we should not forward the `Authorization` header on. This is much the same as to how we don't forward on the header if the host changes. Prior to this fix, `https` to `http` downgrades did not result in the `Authorization` header being removed, only changes to the host. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Users unable to upgrade may consider an alternative approach which would be to use their own redirect middleware. Alternately users may simply disable redirects all together if redirects are not expected or required.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-31043?

It affects 3 products.


Products: Debian Debian Linux, Drupal Drupal, Guzzlephp Guzzle.

## How do I fix CVE-2022-31043?

Upgrade to a fixed version.

## Is CVE-2022-31043 being exploited?

There is no known exploitation of CVE-2022-31043 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31043 and fix it if it is affected.

What it is: CVE-2022-31043 is a high-severity vulnerability in Debian Debian Linux, published on 9 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31043 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31043/ (Markdown: https://insights.sbomify.com/CVE-2022-31043/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31043
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31043
- OSV: https://osv.dev/vulnerability/CVE-2022-31043

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31043/
Summaries are generated and may contain mistakes; the official description above is the record.