CVE-2009-0478: Squid 2.7 to 2.7.STABLE5, 3.0 to 3.0.STABLE12, and 3.1 to 3.1.0.4 allows remote attackers to cause a denial...

Security readout for executives and security teams

This flaw can let a remote attacker crash vulnerable Squid proxy versions by sending a malformed HTTP request. The business impact is service interruption, not data theft, based on the supplied sources. Internet-facing or widely used internal proxies should be treated as higher priority because a crash can disrupt browsing, application routing, or filtering. Exposure is limited to organizations still running the listed legacy Squid versions, especially proxies reachable by untrusted clients. Modern supported Squid deployments are unlikely to be exposed if patched, but old appliances, embedded systems, and forgotten proxy hosts should be checked. Prioritize remediation where Squid is internet-facing, business-critical, or used as a central egress/filtering proxy. For isolated legacy systems, schedule patching through normal maintenance after confirming exposure. The likely impact is outage, so availability criticality should drive urgency. Mitigation focus: Inventory Squid proxy versions across servers, appliances, and managed images.; Upgrade Squid beyond the affected version ranges using vendor-supported packages.; Apply relevant Gentoo, SUSE, Mandriva, Red Hat, or Squid project guidance where applicable..

Prepared

Jun 28, 2026, 11:23 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.