Vulnerability in SSL/TLS parser in Squid HTTP Proxy was found caused by incorrect message size checks and assumptions about the existence of TLS extensions in the SSL/TLS handshake message. This can lead to very high CPU consumption (up to and including 'infinite loop' behaviour). Vulnerable versions are 3.5.0.1 to 3.5.8 (inclusive), which are built with OpenSSL and configured for "SSL-Bump" decryption. This can be exploited remotely. Although there is one layer of authorization applied before this processing to check that the client is allowed to use the proxy, the check is considered generally weak. CVE request: http://seclists.org/oss-sec/2015/q3/577
Created attachment 1074919 [details] Upstream patch
Created squid tracking bugs for this issue: Affects: fedora-all [bug 1264455]
Security Advisory: http://www.squid-cache.org/Advisories/SQUID-2015_3.txt
I believe this was introduced via: http://bazaar.launchpad.net/~squid/squid/trunk/revision/14012 This code never made it into RHEL5, 6, or 7. Statement: This issue did not affect the versions of squid as shipped with Red Hat Enterprise Linux 5, 6, and 7.