Squid Multiple Security Vulnerabilities

Risk

High

Date Discovered

November 5, 2019

Description

Squid is prone to the following vulnerabilities: 1. Multiple buffer-overflow vulnerabilities. 2. An information disclosure vulnerability. 3. A cross-site request-forgery vulnerability. 4. An HTTP request-splitting vulnerability 5. A security-bypass vulnerability. Successful exploits can allow attackers to obtain sensitive information, perform certain unauthorized actions and gain access to the affected application, influence or misrepresent how web content is served, cached, or interpreted, bypass certain security restrictions and to execute arbitrary code in the context of the affected application. Squid versions 2.x through 2.7.STABLE9, 3.x through 3.5.28, and Squid 4.x through 4.8 are vulnerable

Technologies Affected

  • Redhat Enterprise Linux 7
  • Redhat Enterprise Linux 8
  • Squid Squid 2.0.Release
  • Squid Squid 2.1.Patch1
  • Squid Squid 2.1.Patch2
  • Squid Squid 2.1.Pre1
  • Squid Squid 2.1.Pre3
  • Squid Squid 2.1.Pre4
  • Squid Squid 2.1.Release
  • Squid Squid 2.2.Devel3
  • Squid Squid 2.2.Devel4
  • Squid Squid 2.2.Pre1
  • Squid Squid 2.2.Pre2
  • Squid Squid 2.2.Stable1
  • Squid Squid 2.2.Stable2
  • Squid Squid 2.2.Stable3
  • Squid Squid 2.2.Stable4
  • Squid Squid 2.2.Stable5
  • Squid Squid 2.3.Devel2
  • Squid Squid 2.3.Devel3
  • Squid Squid 2.3.Stable1
  • Squid Squid 2.3.Stable2
  • Squid Squid 2.3.Stable3
  • Squid Squid 2.3.Stable4
  • Squid Squid 2.3.Stable5
  • Squid Squid 2.4.Stable1
  • Squid Squid 2.4.Stable2
  • Squid Squid 2.4.Stable3
  • Squid Squid 2.4.Stable4
  • Squid Squid 2.4.Stable6
  • Squid Squid 2.4.Stable7
  • Squid Squid 2.5 Stable5
  • Squid Squid 2.5.Stable1
  • Squid Squid 2.5.Stable2
  • Squid Squid 2.5.Stable3
  • Squid Squid 2.5.Stable4
  • Squid Squid 2.5.Stable5
  • Squid Squid 2.5.Stable6
  • Squid Squid 2.5.Stable7
  • Squid Squid 2.5.Stable8
  • Squid Squid 2.5.Stable9
  • Squid Squid 2.7.STABLE9
  • Squid Squid 3.0
  • Squid Squid 3.1
  • Squid Squid 3.1.21
  • Squid Squid 3.1.22
  • Squid Squid 3.2
  • Squid Squid 3.2.0.10
  • Squid Squid 3.2.11
  • Squid Squid 3.2.12
  • Squid Squid 3.2.13
  • Squid Squid 3.2.3
  • Squid Squid 3.2.4
  • Squid Squid 3.2.5
  • Squid Squid 3.2.7
  • Squid Squid 3.3
  • Squid Squid 3.3.0.1
  • Squid Squid 3.3.0.2
  • Squid Squid 3.3.10
  • Squid Squid 3.3.11
  • Squid Squid 3.3.12
  • Squid Squid 3.3.13
  • Squid Squid 3.3.14
  • Squid Squid 3.3.5
  • Squid Squid 3.3.6
  • Squid Squid 3.3.7
  • Squid Squid 3.3.8
  • Squid Squid 3.3.9
  • Squid Squid 3.4
  • Squid Squid 3.4.10
  • Squid Squid 3.4.13
  • Squid Squid 3.4.14
  • Squid Squid 3.4.3
  • Squid Squid 3.4.4
  • Squid Squid 3.4.6
  • Squid Squid 3.5
  • Squid Squid 3.5.1
  • Squid Squid 3.5.10
  • Squid Squid 3.5.13
  • Squid Squid 3.5.14
  • Squid Squid 3.5.15
  • Squid Squid 3.5.16
  • Squid Squid 3.5.17
  • Squid Squid 3.5.18
  • Squid Squid 3.5.2
  • Squid Squid 3.5.22
  • Squid Squid 3.5.23
  • Squid Squid 3.5.27
  • Squid Squid 3.5.28
  • Squid Squid 4.0
  • Squid Squid 4.0.10
  • Squid Squid 4.0.16
  • Squid Squid 4.0.17
  • Squid Squid 4.0.22
  • Squid Squid 4.0.23
  • Squid Squid 4.0.25
  • Squid Squid 4.0.4
  • Squid Squid 4.0.5
  • Squid Squid 4.0.6
  • Squid Squid 4.0.7
  • Squid Squid 4.0.8
  • Squid Squid 4.0.9
  • Squid Squid 4.1
  • Squid Squid 4.2
  • Squid Squid 4.3
  • Squid Squid 4.4
  • Squid Squid 4.5
  • Squid Squid 4.6
  • Squid Squid 4.7
  • Squid Squid 4.8

Recommendations

Run all software as a nonprivileged user with minimal access rights.
Run all non-administrative software as a non-administrative user with the least amount of privileges required to successfully operate. This will greatly reduce the potential damage that successful exploitation may achieve.

Do not follow links provided by unknown or untrusted sources.
Never follow links provided by unknown or untrusted sources.

Set web browser security to disable the execution of script code or active content.
Since a successful exploit allows the execution of malicious script code in web clients, consider disabling support for script code and active content within the client browser. Note that this mitigation tactic might adversely affect websites that rely on the execution of browser-based script code.

Implement multiple redundant layers of security.
Various memory-protection schemes (such as non-executable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.

Updates are available. Please see the references or vendor advisory for more information.

References

Credits

David Fifield, Jeriko One, Kristoffer Danielsson and Régis Leroy (regilero from Makina Corpus)


© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.

Disclaimer

The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.