[RHSA-2002:089-07] Relaxed LPRng job submission policy

From: bugzillaat_private
Date: Mon Jun 10 2002 - 13:29:53 PDT

  • Next message: Phil Dibowitz: "Broken PMTUD in FreeBSD?"

    ---------------------------------------------------------------------
                       Red Hat, Inc. Red Hat Security Advisory
    
    Synopsis:          Relaxed LPRng job submission policy
    Advisory ID:       RHSA-2002:089-07
    Issue date:        2002-05-16
    Updated on:        2002-06-09
    Product:           Red Hat Linux
    Keywords:          LPRng
    Cross references:  
    Obsoletes:         RHSA-2001:077
    CVE Names:         CAN-2002-0378
    ---------------------------------------------------------------------
    
    1. Topic:
    
    The LPRng print spooler, as shipped in Red Hat Linux 7.x, accepts all
    remote print jobs by default.
    
    2. Relevant releases/architectures:
    
    Red Hat Linux 7.0 - alpha, i386
    
    Red Hat Linux 7.1 - alpha, i386, ia64
    
    Red Hat Linux 7.2 - i386, ia64
    
    Red Hat Linux 7.3 - i386
    
    3. Problem description:
    
    With its default configuration, LPRng will accept job submissions from
    any host, which is not appropriate in a workstation environment.  We
    are grateful to Matthew Caron for pointing out this configuration
    problem.
    
    The Common Vulnerabilities and Exposures project (cve.mitre.org) has
    assigned the name CAN-2002-0378 to this issue.
    
    The updated packages from this advisory change the job submission
    policy (in /etc/lpd.perms) so that jobs from remote hosts are refused
    by default.
    
    Those running print servers may want to adjust this policy as
    appropriate, for example to give access to certain hosts or subnets.
    For details on how to do this see the lpd.perms(5) man page.
    
    Since Red Hat Linux 7.1, default installations include ipchains rules
    blocking remote access to the print spooler IP port; as a result those
    installations already reject remote job submissions.  However, Red Hat
    Linux 7 machines and any machine upgraded to a later release (as 
    opposed to
    having been freshly installed) will not have ipchains rules in place
    by default.
    
    IMPORTANT: There are special instructions for installing this update at
    the end of the "Solution" section below.
    
    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 Red Hat Network.  
    Many
    people find this an easier way to apply updates.  To use Red Hat 
    Network,
    launch the Red Hat Update Agent with the following command:
    
    up2date
    
    This will start an interactive process that will result in the 
    appropriate
    RPMs being upgraded on your system.
    
    After upgrading, you should check that the new configuration file is
    activated. To  do this, type the following command:
    
    grep "X NOT SERVER" /etc/lpd.perms
    
    If this commad returns no output, you will need to put the new
    configuration file in place by typing:
    
    mv /etc/lpd.perms.rpmnew /etc/lpd.perms
    
    5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info):
    
    
    
    6. RPMs required:
    
    Red Hat Linux 7.0:
    
    SRPMS:
    ftp://updates.redhat.com/7.0/en/os/SRPMS/LPRng-3.7.4-23.1.src.rpm
    
    alpha:
    ftp://updates.redhat.com/7.0/en/os/alpha/LPRng-3.7.4-23.1.alpha.rpm
    
    i386:
    ftp://updates.redhat.com/7.0/en/os/i386/LPRng-3.7.4-23.1.i386.rpm
    
    Red Hat Linux 7.1:
    
    SRPMS:
    ftp://updates.redhat.com/7.1/en/os/SRPMS/LPRng-3.7.4-23.1.src.rpm
    
    alpha:
    ftp://updates.redhat.com/7.1/en/os/alpha/LPRng-3.7.4-23.1.alpha.rpm
    
    i386:
    ftp://updates.redhat.com/7.1/en/os/i386/LPRng-3.7.4-23.1.i386.rpm
    
    ia64:
    ftp://updates.redhat.com/7.1/en/os/ia64/LPRng-3.7.4-23.1.ia64.rpm
    
    Red Hat Linux 7.2:
    
    SRPMS:
    ftp://updates.redhat.com/7.2/en/os/SRPMS/LPRng-3.7.4-28.1.src.rpm
    
    i386:
    ftp://updates.redhat.com/7.2/en/os/i386/LPRng-3.7.4-28.1.i386.rpm
    
    ia64:
    ftp://updates.redhat.com/7.2/en/os/ia64/LPRng-3.7.4-28.1.ia64.rpm
    
    Red Hat Linux 7.3:
    
    SRPMS:
    ftp://updates.redhat.com/7.3/en/os/SRPMS/LPRng-3.8.9-4.src.rpm
    
    i386:
    ftp://updates.redhat.com/7.3/en/os/i386/LPRng-3.8.9-4.i386.rpm
    
    
    
    7. Verification:
    
    MD5 sum                          Package Name
    --------------------------------------------------------------------------
    69f458cca66118c3516a836fe81bea0c 7.0/en/os/SRPMS/LPRng-3.7.4-23.1.src.rpm
    a48b696acd1d993e0ed0592ec06e14c0 7.0/en/os/alpha/LPRng-3.7.4-23.1.alpha.rpm
    5443ead6739e417c77b4ce4af28124cc 7.0/en/os/i386/LPRng-3.7.4-23.1.i386.rpm
    69f458cca66118c3516a836fe81bea0c 7.1/en/os/SRPMS/LPRng-3.7.4-23.1.src.rpm
    a48b696acd1d993e0ed0592ec06e14c0 7.1/en/os/alpha/LPRng-3.7.4-23.1.alpha.rpm
    5443ead6739e417c77b4ce4af28124cc 7.1/en/os/i386/LPRng-3.7.4-23.1.i386.rpm
    cbd09b4ebd705011785c4ffdf63bde74 7.1/en/os/ia64/LPRng-3.7.4-23.1.ia64.rpm
    33bad25aff0a6ea45564acac4a3843da 7.2/en/os/SRPMS/LPRng-3.7.4-28.1.src.rpm
    0940df47e5a6a33c1bdeac9d0d2d29e7 7.2/en/os/i386/LPRng-3.7.4-28.1.i386.rpm
    89d7d9f82d2425cc7221665110045260 7.2/en/os/ia64/LPRng-3.7.4-28.1.ia64.rpm
    0a63596e6de46f9e32c2dd3b025c68a5 7.3/en/os/SRPMS/LPRng-3.8.9-4.src.rpm
    a6d4b8b6cb30cddb686c102e27997d6d 7.3/en/os/i386/LPRng-3.8.9-4.i386.rpm
     
    
    These packages are GPG signed by Red Hat, Inc. for security.  Our key
    is available at:
        http://www.redhat.com/about/contact/pgpkey.html
    
    You can verify each package with the following command:
        rpm --checksig  <filename>
    
    If you only wish to verify that each package has not been corrupted or
    tampered with, examine only the md5sum with the following command:
        rpm --checksig --nogpg <filename>
    
    8. References:
    
    
    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0378
    
    
    
    Copyright(c) 2000, 2001, 2002 Red Hat, Inc.
    



    This archive was generated by hypermail 2b30 : Mon Jun 10 2002 - 15:50:53 PDT