Linux Security
    Linux Security
    Linux Security

    Debian: mailman Password leak vulnerability

    Posted By
    A flaw in Mailman 2.1.* allows a remote attacker to retrieve the mailman password of any subscriber by sending a carefully crafted email request to the mailman server.
    Fedora Legacy Update Advisory
    Synopsis:          Updated mailman resolves security vulnerability
    Advisory ID:       FLSA:1734
    Issue date:        2004-07-19
    Product:           Red Hat Linux
    Keywords:          Bugfix
    Cross references:
    CVE Names:         CAN-2004-0412
    - -----------------------------------------------------------------------
    - ---------------------------------------------------------------------
    1. Topic:
    Updated mailman packages that fixes a remote security vulnerability are now 
    2. Relevent releases/architectures:
    Red Hat Linux 9 - i386
    3. Problem description:
    Mailman is software to help manage email discussion lists, much like 
    Majordomo and Smartmail. Unlike most similar products, Mailman gives each 
    mailing list a webpage, and allows users to subscribe, unsubscribe, etc. 
    over the Web. Even the list manager can administer his or her list 
    entirely from the Web. Mailman also integrates most things people want to 
    do with mailing lists, including archiving, mail <-> news gateways, and so 
    A flaw in Mailman 2.1.* allows a remote attacker to retrieve the mailman 
    password of any subscriber by sending a carefully crafted email request to 
    the mailman server.
    A simple patch is available and is fixed upstream in Mailman 2.1.5.
    All users are advised to upgrade to these updated packages, which contain a 
    backported fix and are not vulnerable to this issue.
    Fedora Legacy would like to thank Marc Deslauriers for reporting this 
    4. Solution:
    Before applying this update, make sure all previously released errata 
    relevant to your system have been applied.
    To update all RPMs for your particular architecture, run:
    rpm -Fvh [filenames]
    where [filenames] is a list of the RPMs you wish to upgrade.  Only those 
    RPMs which are currently installed will be updated.  Those RPMs which are 
    not installed but included in the list will not be updated.  Note that you 
    can also use wildcards (*.rpm) if your current directory *only* contains 
    the desired RPMs.
    Please note that this update is also available via yum and apt.  Many 
    people find this an easier way to apply updates.  To use yum issue:
    yum update
    or to use apt:
    apt-get update; apt-get upgrade
    This will start an interactive process that will result in the appropriate 
    RPMs being upgraded on your system.  This assumes that you have yum or 
    apt-get configured for obtaining Fedora Legacy content. Please visit  
    https://www for directions on how to configure yum 
    and apt-get.
    5. Bug IDs fixed:
 - 1734 - CAN-2004-0412 Mailman password retrieval
    6. RPMs required:
    Red Hat Linux 9:
    7. Verification:
    SHA1 sum                                 Package Name
    - ---------------------------------------------------------------------------
    These packages are GPG signed by Fedora Legacy for security.  Our key is 
    available from  https://www.fedoralegacy org/about/security.php
    You can verify each package with the following command:
        rpm --checksig -v 
    If you only wish to verify that each package has not been corrupted or 
    tampered with, examine only the sha1sum with the following command:
    8. References:

    9. Contact:
    The Fedora Legacy security contact is <This email address is being protected from spambots. You need JavaScript enabled to view it.>. More 
    project details at
    - ---------------------------------------------------------------------
    - -- 
    Jesse Keating RHCE	 (
    Fedora Legacy Team	 (
    GPG Public Key		 (
    Was I helpful?  Let others know:

    LinuxSecurity Poll

    Which aspect of server security are you most interested in learning more about?

    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).
    [{"id":"131","title":"Preventing information leakage","votes":"1","type":"x","order":"1","pct":100,"resources":[]},{"id":"132","title":"Firewall considerations","votes":"0","type":"x","order":"2","pct":0,"resources":[]},{"id":"133","title":"Permissions ","votes":"0","type":"x","order":"3","pct":0,"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


    bottom 200

    Please enable / Bitte aktiviere JavaScript!
    Veuillez activer / Por favor activa el Javascript![ ? ]

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