Squid before 3.5.6 does not properly handle CONNECT method peer responses when configured with cache_peer, which allows remote attackers to bypass intended restrictions and gain access to a backend proxy via a CONNECT request.
{ "availability": "No subscription required", "ubuntu_priority": "low", "binaries": [ { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid-cgi" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid-cgi-dbgsym" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid-common" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid-dbg" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid-dbgsym" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid-purge" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid-purge-dbgsym" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squid3" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squidclient" }, { "binary_version": "3.5.12-1ubuntu6", "binary_name": "squidclient-dbgsym" } ] }