Last updated 25 August 2025
Last updated 25 August 2025
Last updated 25 August 2025
http.cc in Squid 3.x before 3.5.15 and 4.x before 4.0.7 proceeds with the storage of certain data after a response-parsing failure, which allows remote HTTP servers to cause a denial of service (assertion failure and daemon exit) via a malformed response.
Squid 3.1 before 3.3.12 and 3.4 before 3.4.4, when SSL-Bump is enabled, allows remote attackers to cause a denial of service (assertion failure) via a crafted range request, related to state management.
A denial of service flaw was found in the way Squid proxy caching server internally processed NULL buffers. A remote, trusted client could use this flaw to cause squid daemon crash (dereference NULL pointer) when processing specially-crafted request.
References: [1] http://www.squid-cache.org/Advisories/SQUID-20103.txt
Upstream patch (against Squid v3.0): [2] http://www.squid-cache.org/Versions/v3/3.0/changesets/squid-3.0-9189.patch
Upstream patch (against Squid v3.1): [3] http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10090.patch
Credit: The vulnerability was discovered by Phil Oester.
A buffer overread flaw was found in the way Squid proxy caching server processed large DNS replies in cases, when no IPv6 resolver was present. A remote attacker could provide DNS reply with large amount of data, leading to denial of service (squid server crash).
Upstream bug report: [1] http://bugs.squid-cache.org/showbug.cgi?id=3021
Relevant upstream changeset: [2] http://bazaar.launchpad.net/~squid/squid/3.1/revision/10072
References: [3] http://marc.info/?l=squid-users&m=128263555724981&w=2 [4] http://bugs.gentoo.org/showbug.cgi?id=334263
CVE Request: [5] http://www.openwall.com/lists/oss-security/2010/08/24/6