An issue was discovered in Squid 4.9 through 4.17 and 5.0.6 through 5.6. Due to inconsistent handling of internal URIs, there can be Exposure of Sensitive Information about clients using the proxy via an HTTPS request to an internal cache manager URL. This is fixed in 5.7.
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squid" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squid-cgi" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squid-cgi-dbgsym" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squid-common" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squid-dbgsym" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squid-purge" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squid-purge-dbgsym" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squidclient" }, { "binary_version": "4.10-1ubuntu1.7", "binary_name": "squidclient-dbgsym" } ] }
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-cgi" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-cgi-dbgsym" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-common" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-dbgsym" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-openssl" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-openssl-dbgsym" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-purge" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squid-purge-dbgsym" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squidclient" }, { "binary_version": "5.2-1ubuntu4.2", "binary_name": "squidclient-dbgsym" } ] }