Multiple memory leaks in tools/cachemgr.cc in cachemgr.cgi in Squid 2.x and 3.x before 3.1.22, 3.2.x before 3.2.4, and 3.3.x before 3.3.0.2 allow remote attackers to cause a denial of service (memory consumption) via (1) invalid Content-Length headers, (2) long POST requests, or (3) crafted authentication credentials.

This update for squid3 fixes the following issues :

  - Multiple issues in pinger ICMP processing.
    (CVE-2014-7141, CVE-2014-7142)

  - CVE-2016-3947: Buffer overrun issue in pinger ICMPv6     processing. (bsc#973782)

  - CVE-2016-4554: fix header smuggling issue in HTTP     Request processing (bsc#979010)

  - Fix multiple Denial of Service issues in HTTP Response     processing. (CVE-2016-2569, CVE-2016-2570,     CVE-2016-2571, CVE-2016-2572, bsc#968392, bsc#968393,     bsc#968394, bsc#968395)

  - Regression caused by the DoS fixes above (bsc#993299)

  - CVE-2016-3948: Fix denial of service in HTTP Response     processing (bsc#973783)

  - CVE-2016-4051: fixes buffer overflow in cachemgr.cgi     (bsc#976553)

  - CVE-2016-4052, CVE-2016-4053, CVE-2016-4054 :

  - fixes multiple issues in ESI processing (bsc#976556)

  - CVE-2016-4556: fixes double free vulnerability in Esi.cc     (bsc#979008)

  - CVE-2015-5400: Improper Protection of Alternate Path     (bsc#938715)

  - CVE-2014-6270: fix off-by-one in snmp subsystem     (bsc#895773)

  - Memory leak in squid3 when using external_acl     (bsc#976708)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for squid3 fixes the following issues :

  - Multiple issues in pinger ICMP processing.
    (CVE-2014-7141, CVE-2014-7142)

  - CVE-2016-3947: Buffer overrun issue in pinger ICMPv6     processing. (bsc#973782)

  - CVE-2016-4554: fix header smuggling issue in HTTP     Request processing (bsc#979010)

  - fix multiple Denial of Service issues in HTTP Response     processing. (CVE-2016-2569, CVE-2016-2570,     CVE-2016-2571, CVE-2016-2572, bsc#968392, bsc#968393,     bsc#968394, bsc#968395)

  - CVE-2016-3948: Fix denial of service in HTTP Response     processing (bsc#973783)

  - CVE-2016-4051: fixes buffer overflow in cachemgr.cgi     (bsc#976553)

  - CVE-2016-4052, CVE-2016-4053, CVE-2016-4054 :

  - fixes multiple issues in ESI processing (bsc#976556)

  - CVE-2016-4556: fixes double free vulnerability in Esi.cc     (bsc#979008)

  - CVE-2015-5400: Improper Protection of Alternate Path     (bsc#938715)

  - CVE-2014-6270: fix off-by-one in snmp subsystem     (bsc#895773)

  - Memory leak in squid3 when using external_acl     (bsc#976708)

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Solaris system is missing necessary patches to address security updates :

  - Multiple memory leaks in tools/cachemgr.cc in     cachemgr.cgi in Squid 2.x and 3.x before 3.1.22, 3.2.x     before 3.2.4, and 3.3.x before 3.3.0.2 allow remote     attackers to cause a denial of service (memory     consumption) via (1) invalid Content-Length headers, (2)     long POST requests, or (3) crafted authentication     credentials. (CVE-2012-5643)

  - cachemgr.cgi in Squid 3.1.x and 3.2.x, possibly 3.1.22,     3.2.4, and other versions, allows remote attackers to     cause a denial of service (resource consumption) via a     crafted request. NOTE: this issue is due to an incorrect     fix for CVE-2012-5643, possibly involving an incorrect     order of arguments or incorrect comparison.
    (CVE-2013-0189)

This squid update includes several security fixes and minor changes.

  -     squid-2.7.x-bnc829084-CVE-2013-4115-BO_request_handling.
    diff Squid advisory SQUID-2013_2, CVE-2013-4115,     [bnc#829084] Specially crafted http requests can trigger     a buffer overflow when squid attempts to resolve an     overly long hostname.

  -     squid-2.7.x-bnc796999-bnc794954-CVE-2012-5643-CVE-2013-0     188-cachemgr_cgi_dos.diff memory leak in cachemgr.cgi     known as CVE-2013-0189, which is the underfixed     CVE-2012-5643 problem. [bnc#796999] [bnc#794954]

  - run logrotate as squid:nogroup [bnc#677335]

- update to 3.1.23 fix for bnc#794954, CVE-2012-5643,     SQUID:2012-1

  - Additional fixes for CVE-2012-5643 / SQUID:2012-1

    - http://www.squid-cache.org/Advisories/SQUID-2012_1.txt

    - http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5643

  - removed 3.1.12 config, nobuilddates, swapdir patch

  - added FSF, config, nobuilddates, swapdir patch

  - added rpmlintrc, service file

  - rebase swapdir patch

The remote host is affected by the vulnerability described in GLSA-201309-22 (Squid: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Squid. Please review       the CVE identifiers referenced below for details.
  Impact :

    A remote attacker may be able to bypass ACL restrictions or cause a       Denial of Service condition.
  Workaround :

    There is no known workaround at this time.

From Red Hat Security Advisory 2013:0505 :

Updated squid packages that fix one security issue and several bugs are now available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.

Squid is a high-performance proxy caching server for web clients that supports FTP, Gopher, and HTTP data objects.

A denial of service flaw was found in the way the Squid Cache Manager processed certain requests. A remote attacker who is able to access the Cache Manager CGI could use this flaw to cause Squid to consume an excessive amount of memory. (CVE-2012-5643)

This update also fixes the following bugs :

* Due to a bug in the ConnStateData::noteMoreBodySpaceAvailable() function, child processes of Squid terminated upon encountering a failed assertion. An upstream patch has been provided and Squid child processes no longer terminate. (BZ#805879)

* Due to an upstream patch, which renamed the HTTP header controlling persistent connections from 'Proxy-Connection' to 'Connection', the NTLM pass-through authentication does not work, thus preventing login.
This update adds the new 'http10' option to the squid.conf file, which can be used to enable the change in the patch. This option is set to 'off' by default. When set to 'on', the NTLM pass-through authentication works properly, thus allowing login attempts to succeed. (BZ#844723)

* When the IPv6 protocol was disabled and Squid tried to handle an HTTP GET request containing an IPv6 address, the Squid child process terminated due to signal 6. This bug has been fixed and such requests are now handled as expected. (BZ#832484)

* The old 'stale if hit' logic did not account for cases where the stored stale response became fresh due to a successful re-validation with the origin server. Consequently, incorrect warning messages were returned. Now, Squid no longer marks elements as stale in the described scenario. (BZ#847056)

* When squid packages were installed before samba-winbind, the wbpriv group did not include Squid. Consequently, NTLM authentication calls failed. Now, Squid correctly adds itself into the wbpriv group if samba-winbind is installed before Squid, thus fixing this bug.
(BZ#797571)

* In FIPS mode, Squid was using private MD5 hash functions for user authentication and network access. As MD5 is incompatible with FIPS mode, Squid could fail to start. This update limits the use of the private MD5 functions to local disk file hash identifiers, thus allowing Squid to work in FIPS mode. (BZ#833086)

* Under high system load, the squid process could terminate unexpectedly with a segmentation fault during reboot. This update provides better memory handling during reboot, thus fixing this bug.
(BZ#782732)

* Squid incorrectly set the timeout limit for client HTTP connections with the value for server-side connections, which is much higher, thus creating unnecessary delays. With this update, Squid uses a proper value for the client timeout limit. (BZ#798090)

* Squid did not properly release allocated memory when generating error page contents, which caused memory leaks. Consequently, the Squid proxy server consumed a lot of memory within a short time period. This update fixes this memory leak. (BZ#758861)

* Squid did not pass the ident value to a URL rewriter that was configured using the 'url_rewrite_program' directive. Consequently, the URL rewriter received the dash character ('-') as the user value instead of the correct user name. Now, the URL rewriter receives the correct user name in the described scenario. (BZ#797884)

* Squid, used as a transparent proxy, can only handle the HTTP protocol. Previously, it was possible to define a URL in which the access protocol contained the asterisk character (*) or an unknown protocol namespace URI. Consequently, an 'Invalid URL' error message was logged to access.log during reload. This update ensures that 'http://' is always used in transparent proxy URLs, and the error message is no longer logged in this scenario. (BZ#720504)

All users of squid are advised to upgrade to these updated packages, which fix these issues. After installing this update, the squid service will be restarted automatically.

Updated squid packages fix security vulnerability :

Due to missing input validation, the Squid cachemgr.cgi tool in Squid before 3.1.22 and 3.2.4 is vulnerable to a denial of service attack when processing specially crafted requests (CVE-2012-5643).

It was discovered that the patch for CVE-2012-5643 was incorrect. A remote attacker could exploit this flaw to perform a denial of service attack (CVE-2013-0189).

Updated squid packages that fix one security issue and several bugs are now available for Red Hat Enterprise Linux 6.

The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.

Squid is a high-performance proxy caching server for web clients that supports FTP, Gopher, and HTTP data objects.

A denial of service flaw was found in the way the Squid Cache Manager processed certain requests. A remote attacker who is able to access the Cache Manager CGI could use this flaw to cause Squid to consume an excessive amount of memory. (CVE-2012-5643)

This update also fixes the following bugs :

* Due to a bug in the ConnStateData::noteMoreBodySpaceAvailable() function, child processes of Squid terminated upon encountering a failed assertion. An upstream patch has been provided and Squid child processes no longer terminate. (BZ#805879)

* Due to an upstream patch, which renamed the HTTP header controlling persistent connections from 'Proxy-Connection' to 'Connection', the NTLM pass-through authentication does not work, thus preventing login.
This update adds the new 'http10' option to the squid.conf file, which can be used to enable the change in the patch. This option is set to 'off' by default. When set to 'on', the NTLM pass-through authentication works properly, thus allowing login attempts to succeed. (BZ#844723)

* When the IPv6 protocol was disabled and Squid tried to handle an HTTP GET request containing an IPv6 address, the Squid child process terminated due to signal 6. This bug has been fixed and such requests are now handled as expected. (BZ#832484)

* The old 'stale if hit' logic did not account for cases where the stored stale response became fresh due to a successful re-validation with the origin server. Consequently, incorrect warning messages were returned. Now, Squid no longer marks elements as stale in the described scenario. (BZ#847056)

* When squid packages were installed before samba-winbind, the wbpriv group did not include Squid. Consequently, NTLM authentication calls failed. Now, Squid correctly adds itself into the wbpriv group if samba-winbind is installed before Squid, thus fixing this bug.
(BZ#797571)

* In FIPS mode, Squid was using private MD5 hash functions for user authentication and network access. As MD5 is incompatible with FIPS mode, Squid could fail to start. This update limits the use of the private MD5 functions to local disk file hash identifiers, thus allowing Squid to work in FIPS mode. (BZ#833086)

* Under high system load, the squid process could terminate unexpectedly with a segmentation fault during reboot. This update provides better memory handling during reboot, thus fixing this bug.
(BZ#782732)

* Squid incorrectly set the timeout limit for client HTTP connections with the value for server-side connections, which is much higher, thus creating unnecessary delays. With this update, Squid uses a proper value for the client timeout limit. (BZ#798090)

* Squid did not properly release allocated memory when generating error page contents, which caused memory leaks. Consequently, the Squid proxy server consumed a lot of memory within a short time period. This update fixes this memory leak. (BZ#758861)

* Squid did not pass the ident value to a URL rewriter that was configured using the 'url_rewrite_program' directive. Consequently, the URL rewriter received the dash character ('-') as the user value instead of the correct user name. Now, the URL rewriter receives the correct user name in the described scenario. (BZ#797884)

* Squid, used as a transparent proxy, can only handle the HTTP protocol. Previously, it was possible to define a URL in which the access protocol contained the asterisk character (*) or an unknown protocol namespace URI. Consequently, an 'Invalid URL' error message was logged to access.log during reload. This update ensures that 'http://' is always used in transparent proxy URLs, and the error message is no longer logged in this scenario. (BZ#720504)

All users of squid are advised to upgrade to these updated packages, which fix these issues. After installing this update, the squid service will be restarted automatically.

A denial of service flaw was found in the way the Squid Cache Manager processed certain requests. A remote attacker who is able to access the Cache Manager CGI could use this flaw to cause Squid to consume an excessive amount of memory. (CVE-2012-5643)

This update also fixes the following bugs :

  - Due to a bug in the     ConnStateData::noteMoreBodySpaceAvailable() function,     child processes of Squid terminated upon encountering a     failed assertion. An upstream patch has been provided     and Squid child processes no longer terminate.

  - Due to an upstream patch, which renamed the HTTP header     controlling persistent connections from     'Proxy-Connection' to 'Connection', the NTLM pass-     through authentication does not work, thus preventing     login. This update adds the new 'http10' option to the     squid.conf file, which can be used to enable the change     in the patch. This option is set to 'off' by default.
    When set to 'on', the NTLM pass-through authentication     works properly, thus allowing login attempts to succeed.

  - When the IPv6 protocol was disabled and Squid tried to     handle an HTTP GET request containing an IPv6 address,     the Squid child process terminated due to signal 6. This     bug has been fixed and such requests are now handled as     expected.

  - The old 'stale if hit' logic did not account for cases     where the stored stale response became fresh due to a     successful re-validation with the origin server.
    Consequently, incorrect warning messages were returned.
    Now, Squid no longer marks elements as stale in the     described scenario.

  - When squid packages were installed before samba-winbind,     the wbpriv group did not include Squid. Consequently,     NTLM authentication calls failed. Now, Squid correctly     adds itself into the wbpriv group if samba-winbind is     installed before Squid, thus fixing this bug.

  - In FIPS mode, Squid was using private MD5 hash functions     for user authentication and network access. As MD5 is     incompatible with FIPS mode, Squid could fail to start.
    This update limits the use of the private MD5 functions     to local disk file hash identifiers, thus allowing Squid     to work in FIPS mode.

  - Under high system load, the squid process could     terminate unexpectedly with a segmentation fault during     reboot. This update provides better memory handling     during reboot, thus fixing this bug.

  - Squid incorrectly set the timeout limit for client HTTP     connections with the value for server-side connections,     which is much higher, thus creating unnecessary delays.
    With this update, Squid uses a proper value for the     client timeout limit.

  - Squid did not properly release allocated memory when     generating error page contents, which caused memory     leaks. Consequently, the Squid proxy server consumed a     lot of memory within a short time period. This update     fixes this memory leak.

  - Squid did not pass the ident value to a URL rewriter     that was configured using the 'url_rewrite_program'     directive. Consequently, the URL rewriter received the     dash character ('') as the user value instead of the     correct user name. Now, the URL rewriter receives the     correct user name in the described scenario.

  - Squid, used as a transparent proxy, can only handle the     HTTP protocol. Previously, it was possible to define a     URL in which the access protocol contained the asterisk     character (*) or an unknown protocol namespace URI.
    Consequently, an 'Invalid URL' error message was logged     to access.log during reload. This update ensures that     'http://' is always used in transparent proxy URLs, and     the error message is no longer logged in this scenario.

After installing this update, the squid service will be restarted automatically.

A denial of service problem in Squid3 initiated via invalid Content-Length headers and memory leaks has been fixed. (CVE-2012-5643 / CVE-2013-0189, SQUID-2012:1)

Also a logrotate permission issue has been fixed.

Squid3, a fully featured Web proxy cache, is prone to a denial of service attack due to memory consumption caused by memory leaks in cachemgr.cgi :

  - CVE-2012-5643     squid's cachemgr.cgi was vulnerable to excessive     resource use. A remote attacker could exploit this flaw     to perform a denial of service attack on the server and     other hosted services.

  - CVE-2013-0189     The original patch for CVE-2012-5643 was incomplete. A     remote attacker still could exploit this flaw to perform     a denial of service attack.

A denial of service problem in Squid via invalid Content-Length headers and memory leaks has been fixed. (CVE-2012-5643 / CVE-2013-0189, SQUID-2012:1)

A denial of service problem in Squid via invalid Content-Length headers and memory leaks has been fixed. (CVE-2012-5643 / CVE-2013-0189, SQUID-2012:1)

Also a logrotate permission issue has been fixed.

Multiple vulnerabilities has been found and corrected in squid (cachemgr.cgi) :

Multiple memory leaks in tools/cachemgr.cc in cachemgr.cgi in Squid 2.x and 3.x before 3.1.22, 3.2.x before 3.2.4, and 3.3.x before 3.3.0.2 allow remote attackers to cause a denial of service (memory consumption) via (1) invalid Content-Length headers, (2) long POST requests, or (3) crafted authentication credentials (CVE-2012-5643).

cachemgr.cgi in Squid 3.1.x and 3.2.x, possibly 3.1.22, 3.2.4, and other versions, allows remote attackers to cause a denial of service (resource consumption) via a crafted request. NOTE: this issue is due to an incorrect fix for CVE-2012-5643, possibly involving an incorrect order of arguments or incorrect comparison (CVE-2013-0189).

The updated packages have been patched to correct these issues.

This is security update that fixes multiple memory leaks in cachemgr tool. (CVE-2013-0189)

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Squid versions prior to 3.1.23, 3.2.x prior to 3.2.6, and 3.3.x prior to 3.3.0.3 are potentially affected by a denial of service vulnerability. The included 'cachemgr.cgi' tool reportedly lacks input validation, which could be abused by any client able to access that tool to perform a denial of service attack on the service host.

Note this fix is a result of an incomplete fix for CVE-2012-5643.

According to its banner, the version of Squid running on the remote host is 2.x or 3.x prior to 3.1.23 / 3.2.6 / 3.3.0.3.  The included 'cachemgr.cgi' tool reportedly lacks input validation, which could be abused by any client able to access that tool to perform a denial of service attack on the service host.

Note this fix is a result of an incomplete fix for CVE-2012-5643.
 Further note that Nessus did not actually test for this issue, but instead has relied on the version in the server's banner.

It was discovered that squid's cachemgr.cgi was vulnerable to excessive resource use. A remote attacker could exploit this flaw to perform a denial of service attack on the server and other hosted services. (CVE-2012-5643)

It was discovered that the patch for CVE-2012-5643 was incorrect. A remote attacker could exploit this flaw to perform a denial of service attack. (CVE-2013-0189).

Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Squid developers report :

Due to missing input validation Squid cachemgr.cgi tool is vulnerable to a denial of service attack when processing specially crafted requests.

This problem allows any client able to reach the cachemgr.cgi to perform a denial of service attack on the service host.

The nature of the attack may cause secondary effects through resource consumption on the host server.

Security update #887962 - DoS (excessive resource consumption) via invalid Content-Length headers or via memory leaks.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

According to its banner, the version of Squid running on the remote host is 2.x or 3.x prior to 3.1.22 / 3.2.4 / 3.3.0.2.  The included 'cachemgr.cgi' tool reportedly lacks input validation, which could be abused by any client able to access that tool to perform a denial of service attack on the service host.  Note that Nessus did not actually test for this issue but has instead relied on the version in the server's banner.

ID	Name	Product	Family	Severity
93294	SUSE SLES11 Security Update : squid3 (SUSE-SU-2016:2089-1)	Nessus	SuSE Local Security Checks	high
93271	SUSE SLES11 Security Update : squid3 (SUSE-SU-2016:1996-1)	Nessus	SuSE Local Security Checks	high
80773	Oracle Solaris Third-Party Patch Update : squid (multiple_vulnerabilities_in_squid)	Nessus	Solaris Local Security Checks	medium
75139	openSUSE Security Update : squid (openSUSE-SU-2013:1436-1)	Nessus	SuSE Local Security Checks	high
75011	openSUSE Security Update : squid3 (openSUSE-SU-2013:0162-1)	Nessus	SuSE Local Security Checks	medium
70182	GLSA-201309-22 : Squid: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	high
68745	Oracle Linux 6 : squid (ELSA-2013-0505)	Nessus	Oracle Linux Local Security Checks	medium
66141	Mandriva Linux Security Advisory : squid (MDVSA-2013:129)	Nessus	Mandriva Local Security Checks	medium
65140	CentOS 6 : squid (CESA-2013:0505)	Nessus	CentOS Local Security Checks	medium
64960	Scientific Linux Security Update : squid on SL6.x i386/x86_64 (20130221)	Nessus	Scientific Linux Local Security Checks	medium
64889	SuSE 11.2 Security Update : squid3 (SAT Patch Number 7336)	Nessus	SuSE Local Security Checks	medium
64867	Debian DSA-2631-1 : squid3 - denial of service	Nessus	Debian Local Security Checks	medium
64866	SuSE 10 Security Update : squid (ZYPP Patch Number 8464)	Nessus	SuSE Local Security Checks	medium
64864	SuSE 11.2 Security Update : squid (SAT Patch Number 7335)	Nessus	SuSE Local Security Checks	medium
64756	RHEL 6 : squid (RHSA-2013:0505)	Nessus	Red Hat Local Security Checks	medium
64745	Mandriva Linux Security Advisory : squid (MDVSA-2013:013)	Nessus	Mandriva Local Security Checks	medium
64514	Fedora 17 : squid-3.2.5-2.fc17 (2013-1625)	Nessus	Fedora Local Security Checks	medium
64513	Fedora 18 : squid-3.2.5-2.fc18 (2013-1616)	Nessus	Fedora Local Security Checks	medium
6850	Squid < 3.1.23 / 3.2.x < 3.2.6 / 3.3.x < 3.3.0.3 cachemgr.cgi DoS	Nessus Network Monitor	Web Servers	low
64501	Squid 2.x / 3.x < 3.1.23 / 3.2.6 / 3.3.0.3 cachemgr.cgi DoS	Nessus	Firewalls	medium
64376	Ubuntu 10.04 LTS / 11.10 / 12.04 LTS / 12.10 : squid, squid3 vulnerabilities (USN-1713-1)	Nessus	Ubuntu Local Security Checks	medium
63366	FreeBSD : squid -- denial of service (c37de843-488e-11e2-a5c9-0019996bc1f7)	Nessus	FreeBSD Local Security Checks	medium
63336	Fedora 16 : squid-3.2.5-1.fc16 (2012-20537)	Nessus	Fedora Local Security Checks	medium
63318	Squid 2.x / 3.x < 3.1.22 / 3.2.4 / 3.3.0.2 cachemgr.cgi DoS	Nessus	Firewalls	medium

Detections

Analytics

CVE-2012-5643

high

Tenable Plugins

high

high

medium

high

medium

high

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

medium

low

medium

medium

medium

medium

medium