Date: 04 March 2009
Click here for printable version
Click here for PGP verifiable version
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
A U S C E R T A L E R T
AL-2009.0014 -- AUSCERT ALERT
[UNIX/Linux]
Squid Proxy Cache Security Update Advisory
5 March 2009
===========================================================================
AusCERT Alert Summary
---------------------
Product: Squid 2.7 -> 2.7.STABLE5
Squid 3.0 -> 3.0.STABLE12
Squid 3.1 -> 3.1.0.4
Publisher: Squid
Operating System: UNIX variants (UNIX, Linux, OSX)
Impact: Denial of Service
Access: Remote/Unauthenticated
CVE Names: CVE-2009-0478
Original Bulletin: http://www.squid-cache.org/Advisories/SQUID-2009_1.txt
Revision History: March 5 2009: Alert Number corrected
February 12 2009: Added CVE Reference
February 6 2009: Made Document Public
February 6 2009: Initial Release
- --------------------------BEGIN INCLUDED TEXT--------------------
__________________________________________________________________
Squid Proxy Cache Security Update Advisory SQUID-2009:1
__________________________________________________________________
Advisory ID: SQUID-2009:1
Date: February 02, 2009
Summary: Denial of service in request processing
Affected versions: Squid 2.7 -> 2.7.STABLE5,
Squid 3.0 -> 3.0.STABLE12,
Squid 3.1 -> 3.1.0.4
Fixed in version: Squid 2.7.STABLE6, 3.0.STABLE13, 3.1.0.5
__________________________________________________________________
http://www.squid-cache.org/Advisories/SQUID-2009_1.txt
__________________________________________________________________
Problem Description:
Due to an internal error Squid is vulnerable to a denial
of service attack when processing specially crafted requests.
__________________________________________________________________
Severity:
This problem allows any client to perform a denial of service
attack on the Squid service.
__________________________________________________________________
Updated Packages:
This bug is fixed by Squid versions 2.7.STABLE6, 3.0.STABLE13,
and 3.1.0.5.
In addition, patches addressing this problem can be found In
our patch archives:
Squid 2.7:
http://www.squid-cache.org/Versions/v2/2.7/changesets/12432.patch
http://www.squid-cache.org/Versions/v2/2.7/changesets/12442.patch
Squid 3.0:
http://www.squid-cache.org/Versions/v3/3.0/changesets/b8964.patch
http://www.squid-cache.org/Versions/v3/3.0/changesets/b8965.patch
Squid 3.1:
http://www.squid-cache.org/Versions/v3/3.1/changesets/b9414.patch
http://www.squid-cache.org/Versions/v3/3.1/changesets/b9418.patch
If you are using a prepackaged version of Squid then please refer
to the package vendor for availability information on updated
packages.
__________________________________________________________________
Determining if your version is vulnerable:
All Squid-2.7 versions up to, and including 2.7.STABLE5 are
vulnerable.
All Squid-3.0 versions up to and including 3.0.STABLE12 are
vulnerable.
All Squid-3.1 beta versions up to and including 3.1.0.4 are
vulnerable.
__________________________________________________________________
Workarounds:
None.
__________________________________________________________________
Contact details for the Squid project:
For installation / upgrade support on binary packaged versions
of Squid: Your first point of contact should be your binary
package vendor.
If your install and build Squid from the original Squid sources
then the squid-users@squid-cache.org mailing list is your primary
support point. For subscription details see
<http://www.squid-cache.org/Support/mailing-lists.html>.
For reporting of non-security bugs in the latest STABLE release
the squid bugzilla database should be used
<http://www.squid-cache.org/bugs/>.
For reporting of security sensitive bugs send an email to the
squid-bugs@squid-cache.org mailing list. It's a closed list
(though anyone can post) and security related bug reports are
treated in confidence until the impact has been established.
__________________________________________________________________
Credits:
The vulnerability was discovered by Joshua Morin, Mikko Varpiola
and Jukka Taimisto from the CROSS project at Codenomicon Ltd.
__________________________________________________________________
Revision history:
2009-02-02 13:12 GMT Initial version
__________________________________________________________________
END
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iD8DBQFJrzQINVH5XJJInbgRAjn7AJ9/Ic9hvSxg/7WfLNsNm/6pHO/GkACffpvc
BoLxj3eRMPNROAyX/NRTipU=
=bk8S
-----END PGP SIGNATURE-----
|