Squid is a widely-used caching proxy server for Linux and Unix platforms. This means that it stores requested Internet objects, such as data on a Web or FTP server, on a machine that is closer to the requesting workstation than the server.
In other words, it redirects object requests from clients (in this case, from Web browsers) to the server.
Proxies provide added layers of security and cache services that make loading processes faster. Squid supports several caching protocols, such as hypertext caching protocols (HTCP), internet cache protocol (ICP), cache array routing protocol (CARP), and web cache communication protocol (WCCP). It also processes caching requests from Domain Name Server (DNS) lookups and Secure Sockets Layer (SSL).
Now that a new version has been announced, let’s see what has changed in Squid 5.2.
Squid 5.2 Highlights
As already mentioned, Squid 5.2 is a security release resolving several vulnerabilities and bugs found in the prior Squid releases.
Due to an out of bounds memory access Squid is vulnerable to an information leak vulnerability when processing WCCPv2 (Web Cache Communication Protocol) messages. This problem allows a WCCPv2 sender to corrupt Squids list of known WCCP routers and divert client traffic to attacker controlled routers.
This attack is limited only to Squid proxy with WCCPv2 enabled and IP spoofing of a router IP address configured as trusted in
squid.conf. Now in Squid 5.2 this has been fixed.
Furthermore, improper certificate validation of TLS server certificates has already been fixed in the latest version. This problem allows a remote server to obtain security trust when the trust is not valid. This indication of trust may be passed along to clients allowing access to unsafe or hijacked services.
In addition to the bugfixes, since v3.5 Squid has incorrectly truncated FTP downloads when the transfer is made in ASCII mode (with
;type= argument). This release can be expected to work when downloading from all FTP servers.