CVE-2005-2917

Description

Squid 2.5.STABLE10 and earlier, while performing NTLM authentication, does not properly handle certain request sequences, which allows attackers to cause a denial of service (daemon restart).

5.0

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 58.16% Top 5%

Vendor Advisory ubuntu.com Vendor Advisory sgi.com Vendor Advisory sco.com Vendor Advisory mandriva.com Vendor Advisory fedoranews.org Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory debian.org Vendor Advisory novell.com Vendor Advisory secunia.com

Affected: n/a n/a

References

Link	Tags
http://www.ubuntu.com/usn/usn-192-1/	vendor advisory
http://securitytracker.com/id?1014920	vdb entry
ftp://patches.sgi.com/support/free/security/advisories/20060401-01-U	vendor advisory
ftp://ftp.sco.com/pub/updates/OpenServer/SCOSA-2005.49/SCOSA-2005.49.txt	vendor advisory
http://secunia.com/advisories/16992	third party advisory patch vendor advisory
http://www.securityfocus.com/bid/14977	vdb entry
http://www.osvdb.org/19607	vdb entry
http://www.mandriva.com/security/advisories?name=MDKSA-2005:181	vendor advisory
https://exchange.xforce.ibmcloud.com/vulnerabilities/24282	vdb entry
http://fedoranews.org/updates/FEDORA--.shtml	vendor advisory
http://secunia.com/advisories/17050	third party advisory
http://www.redhat.com/support/errata/RHSA-2006-0052.html	vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11580	vdb entry signature
http://secunia.com/advisories/19532	third party advisory
http://secunia.com/advisories/17177	third party advisory
http://secunia.com/advisories/19161	third party advisory
http://secunia.com/advisories/17015	third party advisory
http://www.redhat.com/support/errata/RHSA-2006-0045.html	vendor advisory
http://www.debian.org/security/2005/dsa-828	patch vendor advisory
http://www.novell.com/linux/security/advisories/2005_27_sr.html	vendor advisory

Frequently Asked Questions

What is the severity of CVE-2005-2917?: CVE-2005-2917 has been scored as a medium severity vulnerability.
How to fix CVE-2005-2917?: To fix CVE-2005-2917, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2005-2917 being actively exploited in the wild?: It is possible that CVE-2005-2917 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~58% probability that this vulnerability will be exploited by malicious actors in the next 30 days.