QID 356184

squid through 4.14 and 5.x through 5.0.5, in some configurations, allows information disclosure because of an out-of-bounds read in wccp protocol data.
This can be leveraged as part of a chain for remote code execution as nobody. (
( CVE-2021-28116) an issue was discovered in squid before 4.15 and 5.x before 5.0.6.
Due to a buffer-management bug, it allows a denial of service.
When resolving a request with the urn: scheme, the parser leaks a small amount of memory.
However, there is an unspecified attack methodology that can easily trigger a large amount of memory consumption. (
( CVE-2021-28651) an issue was discovered in squid before 4.15 and 5.x before 5.0.6.
Due to incorrect parser validation, it allows a denial of service attack against the cache manager api.
This allows a trusted client to trigger memory leaks that.
Over time, lead to a denial of service via an unspecified short query string.
This attack is limited to clients with cache manager api access privilege. (
( CVE-2021-28652) an issue was discovered in squid 4.x before 4.15 and 5.x before 5.0.6.
If a remote server sends a certain response header over http or https, there is a denial of service.
This header can plausibly occur in benign network traffic. (
( CVE-2021-28662) an issue was discovered in squid before 4.15 and 5.x before 5.0.6.
Due to a memory-management bug, it is vulnerable to a denial of service attack (against all clients using the proxy) via http range request processing. (
( CVE-2021-31806) an issue was discovered in squid before 4.15 and 5.x before 5.0.6.
The issue trigger is a header that can be expected to exist in http traffic without any malicious intent. (

Note: The preceding description block is extracted directly from the security advisory. Using automation, we have attempted to clean and format it as much as possible without introducing additional issues.

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.