REDHAT-BUG-626927: Low severity Squid Squid proxy caching server vulnerability

Published Aug 24, 2010

Updated

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

Affected Software

1 affected component

Squid Squid proxy caching server

Event History

Aug 24, 2010

Data Sourced

05:25 PM

DescriptionSeverityAffected Software

Frequently Asked Questions

What is the severity of REDHAT-BUG-626927?

The severity of REDHAT-BUG-626927 is critical due to its potential to lead to a denial of service by crashing the Squid proxy server.

How do I fix REDHAT-BUG-626927?

To fix REDHAT-BUG-626927, upgrade to the latest version of the Squid proxy caching server that addresses the buffer overread vulnerability.

Who is affected by REDHAT-BUG-626927?

Users running Squid proxy caching server versions vulnerable to the improper processing of large DNS replies are affected by REDHAT-BUG-626927.

What are the potential impacts of REDHAT-BUG-626927?

The potential impacts of REDHAT-BUG-626927 include service disruption through crashes of the Squid proxy caused by crafted DNS replies.

Is there a workaround for REDHAT-BUG-626927?

A workaround for REDHAT-BUG-626927 may involve configuring DNS settings to avoid untrusted inputs until a patch is applied.