LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
How strictly do your users obey your security policies?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
Emily Ratliff: OS Security
DanWalsh LiveJournal
Security Bloggers Network
Latest Newsletters
Linux Security Week: November 17th, 2008
Linux Advisory Watch: November 14th, 2008
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
Mandrake: Updated squid packages fix Print E-mail
User Rating:      How can I rate this item?
Posted by Benjamin D. Thomas   
Mandrake The squid developers discovered that a remote attacker could cause squid to crash via certain DNS responses. The updated packages are patched to fix the problem.
 _______________________________________________________________________

                 Mandrakelinux Security Update Advisory
 _______________________________________________________________________

 Package name:           squid
 Advisory ID:            MDKSA-2005:047
 Date:                   February 24th, 2005

 Affected versions:	 10.0, 10.1, 9.2, Corporate 3.0,
			 Corporate Server 2.1
 ______________________________________________________________________

 Problem Description:

 The squid developers discovered that a remote attacker could cause
 squid to crash via certain DNS responses.
 
 The updated packages are patched to fix the problem.
 _______________________________________________________________________

 References:

  http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-0446
 ______________________________________________________________________

 Updated Packages:
  
 Mandrakelinux 10.0:
 3c386f28371608783183565bd837544b  10.0/RPMS/squid-2.5.STABLE4-2.5.100mdk.i586.rpm
 05401319af15c90fa418571d387495a5  10.0/SRPMS/squid-2.5.STABLE4-2.5.100mdk.src.rpm

 Mandrakelinux 10.0/AMD64:
 c6517cadfb220acf1b247ac0aca9c2e2  amd64/10.0/RPMS/squid-2.5.STABLE4-2.5.100mdk.amd64.rpm
 05401319af15c90fa418571d387495a5  amd64/10.0/SRPMS/squid-2.5.STABLE4-2.5.100mdk.src.rpm

 Mandrakelinux 10.1:
 258f532d766624e4f21936fa31150379  10.1/RPMS/squid-2.5.STABLE6-2.4.101mdk.i586.rpm
 387f2525c892539434ea785f6afc9412  10.1/SRPMS/squid-2.5.STABLE6-2.4.101mdk.src.rpm

 Mandrakelinux 10.1/X86_64:
 c315c0027e40161dedb8e890aeeba963  x86_64/10.1/RPMS/squid-2.5.STABLE6-2.4.101mdk.x86_64.rpm
 387f2525c892539434ea785f6afc9412  x86_64/10.1/SRPMS/squid-2.5.STABLE6-2.4.101mdk.src.rpm

 Corporate Server 2.1:
 b9c9bd1f484d679e97da43ab091bade7  corporate/2.1/RPMS/squid-2.4.STABLE7-2.5.C21mdk.i586.rpm
 8555b2eb1741cf7df61f132fcfa58d15  corporate/2.1/SRPMS/squid-2.4.STABLE7-2.5.C21mdk.src.rpm

 Corporate Server 2.1/X86_64:
 16d583d3930fe2086d9d85de4fb90915  x86_64/corporate/2.1/RPMS/squid-2.4.STABLE7-2.5.C21mdk.x86_64.rpm
 8555b2eb1741cf7df61f132fcfa58d15  x86_64/corporate/2.1/SRPMS/squid-2.4.STABLE7-2.5.C21mdk.src.rpm

 Corporate 3.0:
 cf1542bd32913d9d0124013de664fcf8  corporate/3.0/RPMS/squid-2.5.STABLE4-2.5.C30mdk.i586.rpm
 d953dfffca94d708334237ed052442ee  corporate/3.0/SRPMS/squid-2.5.STABLE4-2.5.C30mdk.src.rpm

 Corporate 3.0/X86_64:
 dcef6aba5715971fd96a36d9ec4bbfff  x86_64/corporate/3.0/RPMS/squid-2.5.STABLE4-2.5.C30mdk.x86_64.rpm
 d953dfffca94d708334237ed052442ee  x86_64/corporate/3.0/SRPMS/squid-2.5.STABLE4-2.5.C30mdk.src.rpm

 Mandrakelinux 9.2:
 9e2f98d688e46f205c2c7cdb6e4d083e  9.2/RPMS/squid-2.5.STABLE3-3.7.92mdk.i586.rpm
 1d6372f63bcccb66a348b7cca51588bd  9.2/SRPMS/squid-2.5.STABLE3-3.7.92mdk.src.rpm

 Mandrakelinux 9.2/AMD64:
 b10ef185be87bd8bb662b0c153016b05  amd64/9.2/RPMS/squid-2.5.STABLE3-3.7.92mdk.amd64.rpm
 1d6372f63bcccb66a348b7cca51588bd  amd64/9.2/SRPMS/squid-2.5.STABLE3-3.7.92mdk.src.rpm
 _______________________________________________________________________

 To upgrade automatically use MandrakeUpdate or urpmi.  The verification
 of md5 checksums and GPG signatures is performed automatically for you.

 All packages are signed by Mandrakesoft for security.  You can obtain
 the GPG public key of the Mandrakelinux Security Team by executing:

  gpg --recv-keys --keyserver pgp.mit.edu 0x22458A98

 You can view other update advisories for Mandrakelinux at:

  http://www.mandrakesoft.com/security/advisories

 If you want to report vulnerabilities, please contact

  security_linux-mandrake.com

 Type Bits/KeyID     Date       User ID
 pub  1024D/22458A98 2000-07-10 Linux Mandrake Security Team
  
 
< Prev   Next >
    
Partner:

 

Latest Features
A Secure Nagios Server
Never Installed a Firewall on Ubuntu? Try Firestarter
Review: Hacking Exposed Linux, Third Edition
Security Features of Firefox 3.0
Review: The Book of Wireless
April 2008 Open Source Tool of the Month: sudo
Open Source Tool of March: ZoneMinder
Yesterday's Edition
Analyzing Malicious SSH Login Attempts

QuickLinks: Comunity , HOWTOs , Blogs , Features , Book Reviews , Networking ,
  Security Projects ,   Latest News ,  Newsletters ,  SELinux ,  Privacy ,  Home,
 Hardening ,   About Us,   Advertise,   Legal Notice,   RSS,   Guardian Digital

(c)Copyright 2008 Guardian Digital, Inc. All rights reserved.