CVE-2005-0095

Public Exploit

Description

The WCCP message parsing code in Squid 2.5.STABLE7 and earlier allows remote attackers to cause a denial of service (crash) via malformed WCCP messages with source addresses that are spoofed to reference Squid's home router and invalid WCCP_I_SEE_YOU cache numbers.

5.0

CVSS

Severity: Medium

CVSS 2.0 •

EPSS 75.84% Top 5%

Vendor Advisory com.br Vendor Advisory trustix.org Vendor Advisory fedoranews.org Vendor Advisory gentoo.org Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory mandriva.com Vendor Advisory novell.com Vendor Advisory redhat.com Vendor Advisory secunia.com Vendor Advisory squid-cache.org Vendor Advisory squid-cache.org

Affected: n/a n/a

References

Link	Tags
http://distro.conectiva.com.br/atualizacoes/?id=a&anuncio=000923	patch vendor advisory
http://www.trustix.org/errata/2005/0003/	patch vendor advisory
http://www.securityfocus.com/bid/12275	vdb entry
http://www.osvdb.org/12886	vdb entry
http://fedoranews.org/updates/FEDORA--.shtml	vendor advisory
http://security.gentoo.org/glsa/glsa-200501-25.xml	patch vendor advisory
http://www.debian.org/security/2005/dsa-651	patch vendor advisory
http://www.squid-cache.org/Versions/v2/2.5/bugs/squid-2.5.STABLE7-wccp_denial_of_service.patch	exploit vendor advisory
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10269	vdb entry signature
http://www.squid-cache.org/Advisories/SQUID-2005_2.txt	patch vendor advisory
http://securitytracker.com/id?1012882	vdb entry
http://www.redhat.com/support/errata/RHSA-2005-061.html	patch vendor advisory
http://www.mandriva.com/security/advisories?name=MDKSA-2005:014	vendor advisory
http://www.novell.com/linux/security/advisories/2005_06_squid.html	patch vendor advisory
http://www.redhat.com/support/errata/RHSA-2005-060.html	patch vendor advisory
http://secunia.com/advisories/13825	third party advisory patch vendor advisory

Frequently Asked Questions

What is the severity of CVE-2005-0095?: CVE-2005-0095 has been scored as a medium severity vulnerability.
How to fix CVE-2005-0095?: To fix CVE-2005-0095, 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-0095 being actively exploited in the wild?: It is possible that CVE-2005-0095 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~76% probability that this vulnerability will be exploited by malicious actors in the next 30 days.