Threat Intelligence Database

guzzlehttp/psr7 is a PSR-7 HTTP message library implementation in PHP. Prior to 2.12.1, guzzlehttp/psr7 did not reject CR/LF characters in certain first-party HTTP start-line fields: the request method, protocol version, and response reason phrase. If an application placed attacker-controlled data into one of those fields and later serialized the PSR-7 message as raw HTTP/1.x, for example with Message::toString() or an equivalent serializer, the serialized message could contain attacker-controlled header lines. The issue can also be reached through Message::parseRequest() or Message::parseResponse() when malformed raw messages are parsed into first-party PSR-7 objects and then serialized again. Creating or modifying a Request, Response, or other PSR-7 object alone is not sufficient. The issue requires the malformed message to be serialized and written to the network, forwarded, replayed, or otherwise processed by software that does not independently reject the malformed start line. This vulnerability is fixed in 2.12.1.

A vulnerability in guzzlehttp/psr7 versions prior to 2.10.2 allows improper input validation of URI host components. This can lead to injection of additional HTTP header lines when user-controlled URLs containing ASCII control characters are used to construct HTTP requests. The issue is patched in version 2.10.2. Applications using affected versions should validate and reject untrusted URI strings containing control characters before constructing PSR-7 Uri or Request objects.

A vulnerability in guzzlehttp/psr7 versions prior to 2.10.2 allows improper validation of the Host header when parsing raw HTTP requests or deriving server request URIs. Malformed Host headers containing URI authority delimiters can cause the request URI host to differ from the original Host header, potentially leading to incorrect routing or forwarding decisions. The issue is patched in version 2.10.2. Users of legacy 1.x versions should apply workarounds as no patch is available.