A denial of service flaw was found in the way the CGI Cache Manager of the Squid proxy caching server processed certain requests. A remote attacker could this this flaw to cause the squid service to consume excessive amount of resources. References: [1] http://www.squid-cache.org/Advisories/SQUID-2012_1.txt [2] https://bugs.gentoo.org/show_bug.cgi?id=447596 [3] https://secunia.com/advisories/51545/ Upstream patches: [4] http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10479.patch (against the 3.1 branch) [5] http://www.squid-cache.org/Versions/v3/3.2/changesets/squid-3.2-11714.patch (against the 3.2 branch)
This issue affects the versions of the squid package, as shipped with Red Hat Enterprise Linux 5 and 6. -- This issue affects the version of the squid package, as shipped with Fedora release of 16. Please schedule an update.
Created squid tracking bugs for this issue Affects: fedora-16 [bug 887964]
CVE Request: [6] http://www.openwall.com/lists/oss-security/2012/12/17/3
The CVE identifier of CVE-2012-5643 has been assigned to this issue: http://www.openwall.com/lists/oss-security/2012/12/17/4
squid-3.2.5-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
Several problems were identified with the original patch, hence upstream SQUID-2012:1 advisory and patches were updated with additional fixes. Updated patches: http://www.squid-cache.org/Versions/v3/3.1/changesets/SQUID-2012_1.patch http://www.squid-cache.org/Versions/v3/3.2/changesets/SQUID-2012_1.patch Individual commits (including commits for the initial fix): http://bazaar.launchpad.net/~squid/squid/3.1/revision/10479 http://bazaar.launchpad.net/~squid/squid/3.1/revision/10483 http://bazaar.launchpad.net/~squid/squid/3.1/revision/10484 http://bazaar.launchpad.net/~squid/squid/3.2/revision/11714 http://bazaar.launchpad.net/~squid/squid/3.2/revision/11743 http://bazaar.launchpad.net/~squid/squid/3.2/revision/11744
(In reply to comment #9) > Several problems were identified with the original patch, hence upstream > SQUID-2012:1 advisory and patches were updated with additional fixes. > The 'incomplete fix for CVE-2012-5643' issue has got an independent identifier of CVE-2013-0189 and is now tracked under dedicated bug 895972.
This issue has been addressed in following products: Red Hat Enterprise Linux 6 Via RHSA-2013:0505 https://rhn.redhat.com/errata/RHSA-2013-0505.html
(In reply to Tomas Hoger from comment #9) > Several problems were identified with the original patch, hence upstream > SQUID-2012:1 advisory and patches were updated with additional fixes. > > Updated patches: > http://www.squid-cache.org/Versions/v3/3.1/changesets/SQUID-2012_1.patch > http://www.squid-cache.org/Versions/v3/3.2/changesets/SQUID-2012_1.patch > > Individual commits (including commits for the initial fix): > http://bazaar.launchpad.net/~squid/squid/3.1/revision/10479 > http://bazaar.launchpad.net/~squid/squid/3.1/revision/10483 > http://bazaar.launchpad.net/~squid/squid/3.1/revision/10484 Additional problem was found in the patch for Squid 3.1. SQUID-2012:1 patch for 3.1 is now updated to include this additional fix: http://bazaar.launchpad.net/~squid/squid/3.1/revision/10486 http://bugs.squid-cache.org/show_bug.cgi?id=3790 Fixes for squid packages in Red Hat Enterprise Linux 6 released via RHSA-2013:0505 contain this issue - bug 990186 was filed to track the regression.
Few notes on the original problem and its mitigation: - cachemgr.cgi is included in the main squid package in Red Hat Enterprise Linux, hence it is installed whenever squid package is installed. - cachemgr.cgi is only exposed if httpd is also installed and running. The squid package does not require httpd, so proxy server can run with only squid service running, but httpd service disabled or not installed. - default configuration in /etc/httpd/conf.d/squid.conf only allow clients form localhost.localdomain to send request to the cachemgr.cgi CGI application. This problem is only exposed to remote hosts/attackers if this default configuration is changed. This problem can be mitigated by not running httpd service, blocking access to the cachemgr.cgi if it's not used, or limiting access to only trusted sources.
Statement: Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.