First published: Sun Sep 05 2010(Updated: )
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] <a href="http://www.squid-cache.org/Advisories/SQUID-2010_3.txt">http://www.squid-cache.org/Advisories/SQUID-2010_3.txt</a> Upstream patch (against Squid v3.0): [2] <a href="http://www.squid-cache.org/Versions/v3/3.0/changesets/squid-3.0-9189.patch">http://www.squid-cache.org/Versions/v3/3.0/changesets/squid-3.0-9189.patch</a> Upstream patch (against Squid v3.1): [3] <a href="http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10090.patch">http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10090.patch</a> Credit: The vulnerability was discovered by Phil Oester.
Affected Software | Affected Version | How to fix |
---|---|---|
Squid Web Proxy Cache | <3.0<3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-630444 is categorized as a denial of service vulnerability.
To fix REDHAT-BUG-630444, update the Squid proxy caching server to a version later than 3.1.
REDHAT-BUG-630444 affects users of Squid versions 3.0 and 3.1.
The impact of REDHAT-BUG-630444 is that a remote, trusted client can crash the Squid daemon.
Yes, REDHAT-BUG-630444 can be exploited by remote users with specially-crafted requests.