CVE-2016-4052: Buffer Overflow
Due to buffer overflow issues Squid is vulnerable to a denial of service attack when processing ESI responses.
Due to incorrect input validation Squid is vulnerable to public information disclosure of the server stack layout when processing ESI responses.
Due to incorrect input validation and buffer overflow Squid is vulnerable to remote code execution when processing ESI responses.
External references:
http://www.squid-cache.org/Advisories/SQUID-20166.txt
Upstream fix:
[RHEL-7] http://www.squid-cache.org/Versions/v3/3.3/changesets/squid-3.3-12697.patch
[Fedora-22] http://www.squid-cache.org/Versions/v3/3.4/changesets/squid-3.4-13235.patch
[Fedora-23] http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3.5-14034.patch
Other sources
Multiple stack-based buffer overflows in Squid 3.x before 3.5.17 and 4.x before 4.0.9 allow remote HTTP servers to cause a denial of service or execute arbitrary code via crafted Edge Side Includes (ESI) responses.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2016-4052?
The severity of CVE-2016-4052 is high due to its potential to cause denial of service and execute arbitrary code.
How do I fix CVE-2016-4052?
To fix CVE-2016-4052, upgrade Squid to version 3.5.17 or 4.0.9 or later.
What systems are affected by CVE-2016-4052?
CVE-2016-4052 affects Squid versions prior to 3.5.17 and 4.x prior to 4.0.9.
How does CVE-2016-4052 exploit work?
CVE-2016-4052 exploits multiple stack-based buffer overflows in Squid by sending crafted Edge Side Includes (ESI) responses.
Can I mitigate CVE-2016-4052 without upgrading?
While upgrading is the best solution, temporary measures may include limiting external access to Squid or configuring firewall rules to manage incoming HTTP responses.