Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
Squid: Multiple vulnerabilities
Detailed Explanation for this Vulnerability Assessment
The remote host is affected by the vulnerability described in GLSA-200501-25
(Squid: Multiple vulnerabilities)
Squid contains a vulnerability in the gopherToHTML function
(CVE-2005-0094) and incorrectly checks the 'number of caches' field
when parsing WCCP_I_SEE_YOU messages (CVE-2005-0095). Furthermore the
NTLM code contains two errors. One is a memory leak in the
fakeauth_auth helper (CVE-2005-0096) and the other is a NULL pointer
dereferencing error (CVE-2005-0097). Finally Squid also contains an
error in the ACL parsing code (CVE-2005-0194).
With the WCCP issue a possible hacker could cause denial of service by
sending a specially crafted UDP packet. With the Gopher issue an
attacker might be able to execute arbitrary code by enticing a user to
connect to a malicious Gopher server. The NTLM issues could lead to
denial of service by memory consumption or by crashing Squid. The ACL
issue could lead to ACL bypass.
There is no known workaround at this time.
All Squid users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=www-proxy/squid-2.5.7-r2"
Network Security Threat Level: Medium
Networks Security ID:
Vulnerability Assessment Copyright: (C) 2005 Michel Arboi
|2 Intel SL9YK Xeon E5335 2.0GHz/8M/1333 Socket 771 CPU Processor.SKU#134320#.
|INTEL XEON E5649 2.533 GHZ CPU SLBZ8 LGA1366 6-CORE
|Lot of 4 Intel Xeon E5504 2.00GHz 4M 4.80 Processor SLBF9.Tested.sku#134362#.
|Intel Xeon E5-2603v2 1800Mhz 10MB Cache Quad Core Processor BX80635E52603V2 NEW
No Discussions have been posted on this vulnerability.