Security readout for executives and security teams
Plain-English summary
This flaw can cause PHP apps using vulnerable Guzzle to send Authorization credentials over unencrypted HTTP after a redirect from HTTPS to HTTP. That can expose API tokens or bearer credentials to interception or logging. Business risk is credential disclosure where applications follow redirects during authenticated outbound requests.
Executive priority
Treat as a high-priority dependency update for systems that make authenticated outbound HTTP calls. The issue can expose reusable credentials, but the provided evidence does not indicate active exploitation or code execution. Prioritize internet-facing services, integration hubs, and platforms with broad API token access.
Technical view
Guzzle failed to remove Authorization when a request to an HTTPS URI was redirected to HTTP on the same host. It already stripped the header on host changes, but not scheme downgrades. Affected versions are before 6.5.7 and 7.0.0 before 7.4.4. Fixes are in 6.5.7 and 7.4.4.
Likely exposure
Exposure is most likely in PHP services, CMS modules, or integrations using Guzzle for authenticated outbound requests with automatic redirects enabled. Drupal and Debian advisories show downstream packaging impact. Systems not using affected Guzzle versions, not sending Authorization, or not following redirects have lower exposure.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. Abuse depends on an HTTPS-to-HTTP redirect while an Authorization header is present. The documented impact is confidentiality loss of credentials, not remote code execution, integrity compromise, or availability loss.
Researcher notes
Focus validation on redirect handling, dependency reachability, and whether Authorization-bearing requests can be redirected from HTTPS to HTTP. The CVSS vector is network, low complexity, no privileges, no user interaction, with high confidentiality impact only. Avoid assuming exposure without affected Guzzle versions and relevant redirect behavior.
Mitigation direction
- Upgrade Guzzle 6.x to 6.5.7 or Guzzle 7.x to 7.4.4 or later.
- Inventory direct and transitive Guzzle dependencies in PHP applications and packaged platforms.
- Apply relevant downstream vendor updates, including Drupal or Debian packages where applicable.
- If upgrade is blocked, use custom redirect middleware that strips Authorization on downgrades.
- Disable automatic redirects where redirects are not expected or required.
Validation and detection
- Check dependency manifests and lockfiles for vulnerable Guzzle versions.
- Confirm deployed containers or servers are not carrying older vendored copies.
- Review outbound HTTP client usage for Authorization headers and automatic redirect behavior.
- Verify vendor advisories for Drupal, Debian, or other packaged distributions in use.
- After updating, run application regression tests covering authenticated outbound requests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-31043 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/guzzle/guzzle/commit/e3ff079b22820c2029d4c2a87796b6a0b8716ad8CVE reference
- https://www.rfc-editor.org/rfc/rfc9110.html#name-redirection-3xxCVE reference
- https://github.com/guzzle/guzzle/security/advisories/GHSA-w248-ffj2-4v5qCVE reference
- https://www.drupal.org/sa-core-2022-011CVE reference
- DSA-5246CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.