==================================================================== CERT-Renater Note d'Information No. 2019/VULN362 _____________________________________________________________________ DATE : 14/11/2019 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running Squid versions prior to 4.9. ===================================================================== http://www.squid-cache.org/Advisories/SQUID-2019_6.txt http://www.squid-cache.org/Advisories/SQUID-2019_7.txt http://www.squid-cache.org/Advisories/SQUID-2019_8.txt http://www.squid-cache.org/Advisories/SQUID-2019_9.txt http://www.squid-cache.org/Advisories/SQUID-2019_10.txt http://www.squid-cache.org/Advisories/SQUID-2019_11.txt _____________________________________________________________________ __________________________________________________________________ Squid Proxy Cache Security Update Advisory SQUID-2019:6 __________________________________________________________________ Advisory ID: SQUID-2019:6 Date: July 12, 2019 Summary: Multiple Cross-Site Scripting issues in cachemgr.cgi. Affected versions: Squid 2.x all releases Squid 3.x -> 3.5.28 Squid 4.x -> 4.8 Fixed in version: Squid 4.9 __________________________________________________________________ http://www.squid-cache.org/Advisories/SQUID-2019_6.txt http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13345 __________________________________________________________________ Problem Description: Due to incorrect input handling Squid cachemgr.cgi tool is vulnerable to multiple cross-site scripting attacks. __________________________________________________________________ Severity: This allows a malicious server to embed URLs in its content such that user credentials and other information can be extracted from a client or administrator with access to the Squid cachemgr.cgi tool URL. __________________________________________________________________ Updated Packages: This bug is fixed by Squid version 4.9. In addition, patches addressing this problem for the stable releases can be found in our patch archives: Squid 3.x: Squid 4: If you are using a prepackaged version of Squid then please refer to the package vendor for availability information on updated packages. __________________________________________________________________ Determining if your version is vulnerable: Squid proxy is not vulnerable. The problem is isolated to the manager CGI interface tool. cachemgr.cgi tool displays its version number in the HTML page footer: All 2.x versions up to and including 2.7.STABLE9 are vulnerable. All 3.x versions up to and including 3.5.28 are vulnerable. All 4.x versions up to and including 4.8 are vulnerable. If your cachemgr.cgi does not display a version it is likely to be one of the older vulnerable versions. __________________________________________________________________ Workarounds: Either; Remove use of the cachemgr.cgi tool. It is only necessary for older proxy management. Modern Squid proxies management reports can be accessed directly. Or, Add CORS protection to the web server running the CGI tool such that remote requests to the cachemgr.cgi tool cannot use query-string parameters. __________________________________________________________________ Contact details for the Squid project: For installation / upgrade support on binary packaged versions of Squid: Your first point of contact should be your binary package vendor. If your install and build Squid from the original Squid sources then the squid-users@lists.squid-cache.org mailing list is your primary support point. For subscription details see . For reporting of non-security bugs in the latest STABLE release the squid bugzilla database should be used . For reporting of security sensitive bugs send an email to the squid-bugs@lists.squid-cache.org mailing list. It's a closed list (though anyone can post) and security related bug reports are treated in confidence until the impact has been established. __________________________________________________________________ Credits: The credentials vulnerability was discovered by Anil Pazvant. Fixed by Amos Jeffries of Treehouse Networks Ltd. Host name vulnerability discovered and fixed by Aaron Costello. __________________________________________________________________ Revision history: 2019-05-27 13:38:06 UTC Initial Report 2019-06-05 15:52:17 UTC CVE Assignment 2019-07-04 01:17:48 UTC Patches Released 2019-07-12 13:00:00 UTC Advisory Released 2019-11-03 16:22:22 UTC Additional patch released __________________________________________________________________ _____________________________________________________________________ __________________________________________________________________ Squid Proxy Cache Security Update Advisory SQUID-2019:7 __________________________________________________________________ Advisory ID: SQUID-2019:7 Date: November 5, 2019 Summary: Heap Overflow issue in URN processing. Affected versions: Squid 3.x -> 3.5.28 Squid 4.x -> 4.8 Fixed in version: Squid 4.9 __________________________________________________________________ http://www.squid-cache.org/Advisories/SQUID-2019_7.txt http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12526 __________________________________________________________________ Problem Description: Due to incorrect buffer management Squid is vulnerable to a heap overflow and possible remote code execution attack when processing URN. __________________________________________________________________ Severity: This allows a malicious client to write a substantial amount of arbitrary data to the heap. Potentially gaining ability to execute arbitrary code. On systems with memory access protections this can result in the Squid process being terminated unexpectedly. Resulting in a denial of service for all clients using the proxy. __________________________________________________________________ Updated Packages: This bug is fixed by Squid version 4.9. In addition, patches addressing this problem for the stable releases can be found in our patch archives: Squid 4: If you are using a prepackaged version of Squid then please refer to the package vendor for availability information on updated packages. __________________________________________________________________ Determining if your version is vulnerable: All Squid-2.x are not vulnerable. All Squid-3.x up to and including 3.5.28 are vulnerable. All Squid-4.x up to and including 4.8 are vulnerable. __________________________________________________________________ Workarounds: Deny urn: protocol URI being proxied to all clients: acl URN proto URN http_access deny URN __________________________________________________________________ Contact details for the Squid project: For installation / upgrade support on binary packaged versions of Squid: Your first point of contact should be your binary package vendor. If your install and build Squid from the original Squid sources then the squid-users@lists.squid-cache.org mailing list is your primary support point. For subscription details see . For reporting of non-security bugs in the latest STABLE release the squid bugzilla database should be used . For reporting of security sensitive bugs send an email to the squid-bugs@lists.squid-cache.org mailing list. It's a closed list (though anyone can post) and security related bug reports are treated in confidence until the impact has been established. __________________________________________________________________ Credits: This vulnerability was discovered by Jeriko One . Fixed by Eduard Bagdasaryan of The Measurement Factory. __________________________________________________________________ Revision history: 2019-05-14 14:56:49 UTC Initial Report 2019-06-05 15:52:17 UTC CVE Assignment 2019-09-15 15:32:30 UTC Patches Released __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ Squid Proxy Cache Security Update Advisory SQUID-2019:8 __________________________________________________________________ Advisory ID: SQUID-2019:8 Date: November 05, 2019 Summary: Multiple issues in URI processing. Affected versions: Squid 3.x -> 3.5.28 Squid 4.x -> 4.8 Fixed in version: Squid 4.9 __________________________________________________________________ http://www.squid-cache.org/Advisories/SQUID-2019_8.txt http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12523 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18676 __________________________________________________________________ Problem Description: Due to improper input validation Squid is vulnerable to security bypass attacks. Attacker can gain access to restricted HTTP servers. Due to incorrect input validation Squid is vulnerable to a buffer overflow which can result in Denial of Service to all clients using the proxy. __________________________________________________________________ Severity: Any remote client may access resources which should be restricted and not available to them. Such as those protected behind client IP ACLs. Attacker could also gain access to manager services when Via header is turned off. Any remote client can perform a Denial of Service on all other clients using the proxy. __________________________________________________________________ Updated Packages: These bugs are fixed by Squid version 4.9. In addition, a patch addressing this problem for stable releases can be found in our patch archives: Squid 4: If you are using a prepackaged version of Squid then please refer to the package vendor for availability information on updated packages. __________________________________________________________________ Determining if your version is vulnerable: Use the command 'squid -v' to view version and build details of your proxy; All Squid 2.x have not been checked. All Squid-3.x up to and including 3.5.28 are vulnerable. All Squid-4.x up to and including 4.8 are vulnerable. __________________________________________________________________ Workaround: Access to manager services can be prevented by enabling the Via header: via on There are no reliable workarounds to prevent access to restricted upstream servers. There are no workarounds for the Denial of Service issue. __________________________________________________________________ Contact details for the Squid project: For installation / upgrade support on binary packaged versions of Squid: Your first point of contact should be your binary package vendor. If you install and build Squid from the original Squid sources then the squid-users@squid-cache.org mailing list is your primary support point. For subscription details see http://www.squid-cache.org/Support/mailing-lists.html. For reporting of non-security bugs in the latest release the squid bugzilla database should be used http://bugs.squid-cache.org/. For reporting of security sensitive bugs send an email to the squid-bugs@squid-cache.org mailing list. It is a closed list (though anyone can post) and security related bug reports are treated in confidence until the impact has been established. __________________________________________________________________ Credits: The security bypass vulnerability was discovered by Jeriko One . The Denial of Service vulnerability was discovered by Kristoffer Danielsson. Fixed by Amos Jeffries, Treehouse Networks Ltd. __________________________________________________________________ Revision history: 2019-05-14 14:56:49 UTC Initial Report 2019-06-05 15:52:17 UTC CVE-2019-12523 Assignment 2019-07-03 01:07:41 UTC Additional Report 2019-11-04 13:43:22 UTC CVE-2019-18676 Assignment __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ Squid Proxy Cache Security Update Advisory SQUID-2019:9 __________________________________________________________________ Advisory ID: SQUID-2019:9 Date: November 05, 2019 Summary: Cross-Site Request Forgery issue in HTTP Request processing. Affected versions: Squid 2.x -> 2.7.STABLE9 Squid 3.x -> 3.5.28 Squid 4.x -> 4.8 Fixed in version: Squid 4.9 __________________________________________________________________ http://www.squid-cache.org/Advisories/SQUID-2019_9.txt http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18677 __________________________________________________________________ Problem Description: Due to incorrect message processing Squid configured with append_domain can inappropriately redirect traffic to origins it should not be delivered to. __________________________________________________________________ Severity: This issue allows attackers to hide origin servers for phishing attacks or malware download URLs. This issue is restricted to proxies with append_domain configured. It is relatively easy for attackers to probe and determine whether a target network proxy has this directive along with its value. __________________________________________________________________ Updated Packages: This bug is fixed by Squid version 4.9. In addition, patches addressing this problem for the stable releases can be found in our patch archives: Squid 3.5: Squid 4: If you are using a prepackaged version of Squid then please refer to the package vendor for availability information on updated packages. __________________________________________________________________ Determining if your version is vulnerable: All Squid without append_domain configured are not vulnerable. All Squid-2.x up to and including 2.7.STABLE9 with append_domain configured are vulnerable. All Squid-3.x up to and including 3.5.28 with append_domain configured are vulnerable. All Squid-4.x up to and including 4.8 with append_domain configured are vulnerable. To determine whether append_domain is configured use the command: squid -k parse | grep append_domain __________________________________________________________________ Workarounds: Remove append_domain configuration settings from squid.conf. The append_domain feature is redundant when /etc/resolv.conf is used to determine hostnames. However, please note that use of /etc/resolv.conf may require removal of dns_nameservers and other redundant DNS directives. __________________________________________________________________ Contact details for the Squid project: For installation / upgrade support on binary packaged versions of Squid: Your first point of contact should be your binary package vendor. If your install and build Squid from the original Squid sources then the squid-users@lists.squid-cache.org mailing list is your primary support point. For subscription details see . For reporting of non-security bugs in the latest STABLE release the squid bugzilla database should be used . For reporting of security sensitive bugs send an email to the squid-bugs@lists.squid-cache.org mailing list. It's a closed list (though anyone can post) and security related bug reports are treated in confidence until the impact has been established. __________________________________________________________________ Credits: This vulnerability was discovered by Kristoffer Danielsson. Fixed by Amos Jeffries of Treehouse Networks Ltd. __________________________________________________________________ Revision history: 2019-06-26 21:43:49 UTC Initial Report 2019-07-12 03:08:00 UTC Patches Released 2019-11-04 13:43:22 UTC CVE-2019-18677 Assignment __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ Squid Proxy Cache Security Update Advisory SQUID-2019:10 __________________________________________________________________ Advisory ID: SQUID-2019:10 Date: November 05, 2019 Summary: HTTP Request Splitting issue in HTTP message processing. Affected versions: Squid 3.0 -> 3.5.28 Squid 4.x -> 4.8 Fixed in version: Squid 4.9 __________________________________________________________________ http://www.squid-cache.org/Advisories/SQUID-2019_10.txt http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18678 __________________________________________________________________ Problem Description: Due to incorrect message parsing Squid is vulnerable to an HTTP request splitting issue. __________________________________________________________________ Severity: This issue allows attackers to smuggle HTTP requests through frontend software to a Squid which splits the HTTP Request pipeline differently. The resulting Response messages corrupt caches between client and Squid with attacker controlled content at arbitrary URLs.. Effects are isolated to software between the attacker client and Squid. There are no effects on Squid itself, nor any upstream servers. __________________________________________________________________ Updated Packages: This bug is fixed by Squid version 4.9. In addition, a patch addressing this problem for the stable releases can be found in our patch archives: Squid 4: If you are using a prepackaged version of Squid then please refer to the package vendor for availability information on updated packages. __________________________________________________________________ Determining if your version is vulnerable: All Squid-2.x have not been checked. All Squid-3.x up to and including 3.5.28 are vulnerable. All Squid-4.x up to and including 4.8 are vulnerable. __________________________________________________________________ Workarounds: There are no workarounds for this vulnerability. __________________________________________________________________ Contact details for the Squid project: For installation / upgrade support on binary packaged versions of Squid: Your first point of contact should be your binary package vendor. If your install and build Squid from the original Squid sources then the squid-users@lists.squid-cache.org mailing list is your primary support point. For subscription details see . For reporting of non-security bugs in the latest STABLE release the squid bugzilla database should be used . For reporting of security sensitive bugs send an email to the squid-bugs@lists.squid-cache.org mailing list. It's a closed list (though anyone can post) and security related bug reports are treated in confidence until the impact has been established. __________________________________________________________________ Credits: This vulnerability was discovered by by Regis Leroy (regilero from Makina Corpus). Fixed by Amos Jeffries of Treehouse Networks Ltd. __________________________________________________________________ Revision history: 2019-07-24 11:52:51 UTC Initial Report 2019-09-11 02:52:52 UTC Patches Released 2019-11-04 13:43:22 UTC CVE Assignment __________________________________________________________________ __________________________________________________________________ __________________________________________________________________ Squid Proxy Cache Security Update Advisory SQUID-2019:11 __________________________________________________________________ Advisory ID: SQUID-2019:11 Date: November 05, 2019 Summary: Information Disclosure issue in HTTP Digest Authentication. Affected versions: Squid 2.x -> 2.7.STABLE9 Squid 3.x -> 3.5.28 Squid 4.x -> 4.8 Fixed in version: Squid 4.9 __________________________________________________________________ http://www.squid-cache.org/Advisories/SQUID-2019_11.txt http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-18679 __________________________________________________________________ Problem Description: Due to incorrect data management Squid is vulnerable to a information disclosure when processing HTTP Digest Authentication. __________________________________________________________________ Severity: Nonce tokens contain the raw byte value of a pointer which sits within heap memory allocation. This information reduces ASLR protections and may aid attackers isolating memory areas to target for remote code execution attacks. __________________________________________________________________ Updated Packages: This bug is fixed by Squid version 4.9. In addition, a patch addressing this problem for the stable releases can be found in our patch archives: Squid 4: If you are using a prepackaged version of Squid then please refer to the package vendor for availability information on updated packages. __________________________________________________________________ Determining if your version is vulnerable: All Squid-2.x up to and including 2.7.STABLE9 are vulnerable. All Squid-3.x up to and including 3.5.28 are vulnerable. All Squid-4.x up to and including 4.8 are vulnerable. __________________________________________________________________ Workarounds: Either; Remove 'auth_param digest ...' configuration settings from squid.conf. Or, Build Squid with --disable-auth-digest __________________________________________________________________ Contact details for the Squid project: For installation / upgrade support on binary packaged versions of Squid: Your first point of contact should be your binary package vendor. If your install and build Squid from the original Squid sources then the squid-users@lists.squid-cache.org mailing list is your primary support point. For subscription details see . For reporting of non-security bugs in the latest STABLE release the squid bugzilla database should be used . For reporting of security sensitive bugs send an email to the squid-bugs@lists.squid-cache.org mailing list. It's a closed list (though anyone can post) and security related bug reports are treated in confidence until the impact has been established. __________________________________________________________________ Credits: This vulnerability was discovered and fixed by David Fifield. __________________________________________________________________ Revision history: 2019-08-05 06:15:36 UTC Initial Report 2019-10-20 18:59:08 UTC Patches Released 2019-11-04 13:43:22 UTC CVE Assignment __________________________________________________________________ ========================================================= + CERT-RENATER | tel : 01-53-94-20-44 + + 23/25 Rue Daviel | fax : 01-53-94-20-41 + + 75013 Paris | email:cert@support.renater.fr + =========================================================