guzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via Referer
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| guzzle | guzzle | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Guzzlephp | Guzzle |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-h95v-h523-3mw8 | Guzzle: URI fragments disclosed in redirect Referer headers |
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.372% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | guzzlehttp/guzzle versions before 7.15.1 contain an information disclosure vulnerability in RedirectMiddleware. When the optional allow_redirects.referer setting is enabled, the middleware copies the URI fragment (the portion after '#') from the referring request into the generated Referer header when following a same-scheme redirect (e.g., HTTPS to HTTPS). An attacker who controls the redirect destination can read this fragment from the incoming Referer header, potentially disclosing one-time login secrets, access tokens, state values, or other sensitive client data to a server never meant to receive it. The referer setting is disabled by default. Fixed in 7.15.1, which strips the fragment before generating the Referer value. | |
| Title | guzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via Referer | |
| First Time appeared |
Guzzlephp
Guzzlephp guzzle |
|
| Weaknesses | CWE-201 | |
| CPEs | cpe:2.3:a:guzzlephp:guzzle:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Guzzlephp
Guzzlephp guzzle |
|
| References |
| |
| Metrics |
cvssV3_1
|