Impact
guzzlehttp/psr7 improperly interpreted malformed Host header values when constructing request URIs from inbound request data. This issue concerns inbound request parsing and server request construction. It does not require serializing a PSR-7 request, and it is not part of the normal outbound request-sending path used by guzzlehttp/guzzle.
A vulnerable flow is:
- An attacker controls a raw HTTP request or server variable containing a
Host value.
- The
Host value contains URI authority delimiters, such as trusted.example@evil.example.
guzzlehttp/psr7 uses that value to construct a URI.- The URI parser treats the portion before
@ as userinfo and the portion after @ as the URI host.
- The resulting PSR-7 request URI host differs from the original
Host header value.
For example, Host: trusted.example@evil.example can result in a PSR-7 URI whose host is evil.example, while the original Host header value remains trusted.example@evil.example.
Applications are affected if they parse attacker-controlled raw HTTP requests with GuzzleHttp\Psr7\Message::parseRequest() or the legacy 1.x GuzzleHttp\Psr7\parse_request() function, or if they build server requests from attacker-controlled server variables with GuzzleHttp\Psr7\ServerRequest::fromGlobals() or GuzzleHttp\Psr7\ServerRequest::getUriFromGlobals(), and then rely on the resulting URI host for routing, allow-list checks, credential selection, or forwarding decisions. Applications using guzzlehttp/psr7 only through Guzzle's standard HTTP client APIs are not expected to be affected. In affected forwarding or gateway scenarios, this may cause requests or credentials to be sent to an unintended host.
Patches
The issue is patched in 2.10.2 and later. 1.x is end-of-life and will not receive a patch.
Workarounds
If you cannot upgrade immediately, validate Host values before passing untrusted request data to Message::parseRequest(), legacy 1.x parse_request(), ServerRequest::fromGlobals(), or ServerRequest::getUriFromGlobals().
Accept only uri-host [ ":" port ]. Reject values containing whitespace, control characters, userinfo (@), path (/ or \), query (?), fragment (#), malformed IP literals or bracket syntax, or invalid port syntax.
Do not validate Host by prefixing it with http:// and passing it to parse_url(), because that can reinterpret malformed values as URI userinfo and host.
References
References
edorian Reporter
Impact
guzzlehttp/psr7improperly interpreted malformedHostheader values when constructing request URIs from inbound request data. This issue concerns inbound request parsing and server request construction. It does not require serializing a PSR-7 request, and it is not part of the normal outbound request-sending path used byguzzlehttp/guzzle.A vulnerable flow is:
Hostvalue.Hostvalue contains URI authority delimiters, such astrusted.example@evil.example.guzzlehttp/psr7uses that value to construct a URI.@as userinfo and the portion after@as the URI host.Hostheader value.For example,
Host: trusted.example@evil.examplecan result in a PSR-7 URI whose host isevil.example, while the original Host header value remainstrusted.example@evil.example.Applications are affected if they parse attacker-controlled raw HTTP requests with
GuzzleHttp\Psr7\Message::parseRequest()or the legacy 1.xGuzzleHttp\Psr7\parse_request()function, or if they build server requests from attacker-controlled server variables withGuzzleHttp\Psr7\ServerRequest::fromGlobals()orGuzzleHttp\Psr7\ServerRequest::getUriFromGlobals(), and then rely on the resulting URI host for routing, allow-list checks, credential selection, or forwarding decisions. Applications usingguzzlehttp/psr7only through Guzzle's standard HTTP client APIs are not expected to be affected. In affected forwarding or gateway scenarios, this may cause requests or credentials to be sent to an unintended host.Patches
The issue is patched in
2.10.2and later.1.xis end-of-life and will not receive a patch.Workarounds
If you cannot upgrade immediately, validate Host values before passing untrusted request data to
Message::parseRequest(), legacy 1.xparse_request(),ServerRequest::fromGlobals(), orServerRequest::getUriFromGlobals().Accept only
uri-host [ ":" port ]. Reject values containing whitespace, control characters, userinfo (@), path (/or\), query (?), fragment (#), malformed IP literals or bracket syntax, or invalid port syntax.Do not validate Host by prefixing it with
http://and passing it toparse_url(), because that can reinterpret malformed values as URI userinfo and host.References
References