guzzlehttp/psr7 vulnerabilities

In the guzzlehttp/psr7 library prior to version 2.12.3, the Uri::assertValidHost() function does not reject invalid URI host components that may contain authority delimiters, embedded ports, or malformed IPv6 brackets. This causes Uri::getHost() to potentially return a value different from the actual URI authority, which can lead to errors in security or routing decisions.

The guzzlehttp/psr7 library before version 2.12.1 did not reject CR/LF characters in certain HTTP start-line fields (request method, protocol version, response reason phrase). An attacker can inject controlled data into these fields, and after serializing the PSR-7 message to raw HTTP/1.x (e.g., via Message::toString()), it may lead to HTTP header injection.

The guzzlehttp/psr7 library in versions prior to 2.10.2 did not reject ASCII control characters, whitespace, or DEL in URI host components. This can lead to the injection of additional headers by an attacker, posing a risk to applications using user-controlled URLs.

The guzzlehttp/psr7 library in versions prior to 2.10.2 contains improper Host header validation, which can lead to incorrect URI processing in HTTP requests. An attacker can provide a malicious Host header, resulting in a discrepancy between the original value and the URI host value.