Debian: New spamassassin packages fix potential DOS

    Date07 Jul 2005
    CategoryDebian
    4127
    Posted ByJoe Shakespeare
    A vulnerability was recently found in the way that SpamAssassin parses certain email headers. This vulnerability could cause SpamAssassin to consume a large number of CPU cycles when processing messages containing these headers, leading to a potential denial of service (DOS) attack.
    - ------------------------------------------------------------------------
    Debian Security Advisory DSA 736-2                   This email address is being protected from spambots. You need JavaScript enabled to view it.
    http://www.debian.org/security/                            Michael Stone
    July 07, 2005                         http://www.debian.org/security/faq
    - ------------------------------------------------------------------------
    
    Package        : spamassassin
    Vulnerability  : mail header parsing error
    Problem type   : remote DOS
    Debian-specific: no
    CVE Id(s)      : CAN-2005-1266
    Debian Bug     : 314447
    
    A vulnerability was recently found in the way that SpamAssassin parses
    certain email headers. This vulnerability could cause SpamAssassin to
    consume a large number of CPU cycles when processing messages containing
    these headers, leading to a potential denial of service (DOS) attack. 
    
    The version of SpamAssassin in the old stable distribution (woody) is
    not vulnerable.
    
    For the stable distribution (sarge), this problem has been fixed in
    version 3.0.3-2. Note that packages are not yet ready for certain
    architectures; these will be released as they become available.
    
    For the unstable distribution (sid), this problem has been fixed in
    version 3.0.4-1.
    
    The only change since DSA 736-1 is the addition of packages for certain
    architectures that were not available at the time of the original
    advisory.
    
    We recommend that you upgrade your sarge or sid spamassassin package.
    
    Upgrade instructions
    - --------------------
    
    wget url
            will fetch the file for you
    dpkg -i file.deb
            will install the referenced file.
    
    If you are using the apt-get package manager, use the line for
    sources.list as given below:
    
    apt-get update
            will update the internal database
    apt-get upgrade
            will install corrected packages
    
    You may use an automated update by adding the resources from the
    footer to the proper configuration.
    
    
    Debian 3.1 (sarge)
    - ------------------
    
      sarge was released for alpha, arm, hppa, i386, ia64, m68k, mips, mipsel, powerpc, s390 and sparc. Packages were released for all but arm and hppa in DSA 736-1.
    
      arm architecture (ARM)
    
        http://security.debian.org/pool/updates/main/s/spamassassin/spamc_3.0.3-2_arm.deb
          Size/MD5 checksum:    58362 cf463ef4d601f3f6502f891eef928451
    
      hppa architecture (HP PA RISC)
    
        http://security.debian.org/pool/updates/main/s/spamassassin/spamc_3.0.3-2_hppa.deb
          Size/MD5 checksum:    60236 4f6c26a0c8ac1249aa38c17040b18d97
    
    
    - -------------------------------------------------------------------------------
    For apt-get: deb http://security.debian.org/ stable/updates main
    For dpkg-ftp: ftp://security.debian.org/debian-security dists/stable/updates/main
    Mailing list: This email address is being protected from spambots. You need JavaScript enabled to view it.
    
    You are not authorised to post comments.

    Comments powered by CComment

    LinuxSecurity Poll

    What do you think of the articles on LinuxSecurity?

    No answer selected. Please try again.
    Please select either existing option or enter your own, however not both.
    Please select minimum 0 answer(s) and maximum 3 answer(s).
    /main-polls/24-what-do-you-think-of-the-quality-of-the-articles-on-linuxsecurity?task=poll.vote&format=json
    24
    radio
    [{"id":"87","title":"Excellent, don't change a thing!","votes":"67","type":"x","order":"1","pct":57.26,"resources":[]},{"id":"88","title":"Should be more technical","votes":"16","type":"x","order":"2","pct":13.68,"resources":[]},{"id":"89","title":"Should include more HOWTOs","votes":"34","type":"x","order":"3","pct":29.06,"resources":[]}]["#ff5b00","#4ac0f2","#b80028","#eef66c","#60bb22","#b96a9a","#62c2cc"]["rgba(255,91,0,0.7)","rgba(74,192,242,0.7)","rgba(184,0,40,0.7)","rgba(238,246,108,0.7)","rgba(96,187,34,0.7)","rgba(185,106,154,0.7)","rgba(98,194,204,0.7)"]350
    bottom200

    We use cookies to provide and improve our services. By using our site, you consent to our Cookie Policy.