Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2022-31091— Change in port should be considered a change in origin in Guzzle

Quick assessment

Affected
guzzle guzzle
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Guzzle是guzzlehttp个人开发者的一个 PHP HTTP 客户端，可以轻松发送 HTTP 请求并轻松与 Web 服务集成。 Guzzle 存在信息泄露漏洞。攻击者利用该漏洞通过 Authorization / Cookie Headers 绕过对 Guzzle 数据的访问限制，以便读取敏感信息。

CVSS 7.7 · High EPSS 1.57% · P75

Possible ATT&CK Techniques 1 AI

T1552.001 · Credentials In Files
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2022-31091

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Change in port should be considered a change in origin in Guzzle
Source: CVE Program / CVE List V5
Vulnerability Description
Guzzle, an extensible PHP HTTP client. `Authorization` and `Cookie` headers on requests are sensitive information. In affected versions on making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port. An alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
信息暴露
Source: CVE Program / CVE List V5
Vulnerability Title
Guzzle 信息泄露漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Guzzle是guzzlehttp个人开发者的一个 PHP HTTP 客户端，可以轻松发送 HTTP 请求并轻松与 Web 服务集成。 Guzzle 存在信息泄露漏洞。攻击者利用该漏洞通过 Authorization / Cookie Headers 绕过对 Guzzle 数据的访问限制，以便读取敏感信息。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
guzzle guzzle < 6.5.8 -

II. Public POCs for CVE-2022-31091

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-31091

请登录查看更多情报信息。

Patches & Fixes for CVE-2022-31091 (1)

Vendor Advisories for CVE-2022-31091 (2)

IV. Related Vulnerabilities

Same product: guzzle
Same vendor: guzzle
Same weakness: CWE-200