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
Check for the version of the squid package
Detailed Explanation for this Vulnerability Assessment
The remote host is missing the patch for the advisory SUSE-SA:2005:053 (squid).
This update of the Squid web-proxy fixes two remotely exploitable denial
of service vulnerabilities.
One can be triggered by aborting a request (CVE-2005-2794) due to a faulty
The other one occurs in sslConnectTimeout while handling malformated
The latter one does not affect SUSE LINUX 9.3.
2) Solution or Workaround
There are no workarounds known.
3) Special Instructions and Notes
Please restart the Squid web-proxy after the update.
4) Package Location and Checksums
The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command
to apply the update, replacing
downloaded RPM package.
Solution : http://www.suse.de/security/advisories/2005_53_squid.html
Network Security Threat Level: Medium
Networks Security ID:
Vulnerability Assessment Copyright: This script is Copyright (C) 2005 Tenable Network Security
|SOYO 4SAW2 MOTHERBOARD SOCKET 3 VESA ISA PCI
|Gigabyte Z390 Aorus Master (Intel Lga1151/Z390/Atx/3Xm.2 Thermal Guard/Onboard A
|1pc 100% test IM483I (by EMS or DHL 90days Warranty) #j1688
|1PCS USED AND WORKING 100840438 100840430 I/O (DHL or EMS 90days Warranty) #A001
No Discussions have been posted on this vulnerability.