The correction for CAN-2003-0144 for the old stable distribution (potato) was a little bit too strict apparently and this update corrects this.. - -------------------------------------------------------------------------- Debian Security Advisory DSA 267-2
A buffer overflow has been discovered in lpr, a BSD lpr/lpd lineprinter spooling system.. - -------------------------------------------------------------------------- Debian Security Advisory DSA 267-1
Authentication and configuration vulnerabilities that could lead to a root compromise exist.. Package lpr Synopsis New lpr packages available Advisory ID RHSA-2000:002-01 Issue Date 2000-01-07 Updated on 2000-01-07 Keywords lpr lpd DNS sendmail 1. Topic: New lpr packages are available to fix two security problems in lpd. 2. Problem description: Two security vulnerabilities exist in the lpd (line printer daemon) shipped with the lpr package. First, authentication was not thorough enough. If a remote user was able to control their own DNS so that their IP address resolved to the hostname of the print server, access would be granted, when it should not be. Secondly, it was possible in the control file of a print job to specify arguments to sendmail. By careful manipulation of control and data files, this could cause sendmail to be executed with a user-specified configuration file. This could lead very easily to a root compromise. It is recommended that all users of Red Hat Linux using the lpr package (which is required to print) upgrade to the fixed packages. Thanks go to DilDog (dildog@l0pht.com) for noting the vulnerability. If you are experiencing problems with local printing in Red Hat Linux 6.1, make sure that you have: alias parport_lowlevel parport_pc in your /etc/conf.modules file. 3. Bug IDs fixed: (see bugzilla for more information) 4. Relevant releases/architectures: Red Hat Linux 6.1, all architectures 5. Obsoleted by: None 6. Conflicts with: None 7. RPMs required: Intel: lpr-0.48-1.i386.rpm Alpha: lpr-0.48-1.alpha.rpm SPARC: lpr-0.48-1.sparc.rpm Source: lpr-0.48-1.src.rpm 8. Solution: For each RPM for your particular architecture, run: rpm-Uvh filename where filename is the name of the RPM. Then, restart lpd: /etc/rc.d/init.d/lpd restart 9. Verification: MD5 sum Package Name ------------------------------------------------------------------------- 78f2220331189e723eab944b53d0710e i386/lpr-0.48-1.i386.rpm 3fcb89eb1a76741a505d3eeeddfa3674 alpha/lpr-0.48-1.alpha.rpm 441cfee04428ca215d98d9ce3d20bc4d sparc/lpr-0.48-1.sparc.rpm 55c6a740b03569919ec08992257cad96 SRPMS/lpr-0.48-1.src.rpm These packages are GPG signed by Red Hat, Inc. for security. Our key is available at: About 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 Note that you need RPM > = 3.0 to check GnuPG keys. 10. References: Thanks to
New lpr packages are available to fix two security problems in lpd.. ` --------------------------------------------------------------------- Red Hat, Inc. Security Advisory Synopsis: New lpr packages available Advisory ID: RHSA-2000:002-01 Issue date: 2000-01-07 Updated on: 2000-01-07 Keywords: lpr lpd DNS sendmail Cross references: --------------------------------------------------------------------- 1. Topic: New lpr packages are available to fix two security problems in lpd. 2. Relevant releases/architectures: Red Hat Linux 4.x, all architectures Red Hat Linux 5.x, all architectures Red Hat Linux 6.x, all architectures 3. Problem description: Two security vulnerabilities exist in the lpd (line printer daemon) shipped with the lpr package. First, authentication was not thorough enough. If a remote user was able to control their own DNS so that their IP address resolved to the hostname of the print server, access would be granted, when it should not be. Secondly, it was possible in the control file of a print job to specify arguments to sendmail. By careful manipulation of control and data files, this could cause sendmail to be executed with a user-specified configuration file. This could lead very easily to a root compromise. It is recommended that all users of Red Hat Linux using the lpr package (which is required to print) upgrade to the fixed packages. Thanks go to DilDog (
The file access permissions aren't properly checked by the lpr and lpd program. . ______________________________________________________________________________ SuSE Security Announcement Package: lprold
There are potential problems with file access checking in the lpr and lpd programs. These could allow users to potentially print files they do not have access to. Also, there are bugs in remote printing in the lpd that shipped with Red Hat Linux 6.1. . Red Hat, Inc. Security Advisory Package lpr Synopsis File access problems in lpr/lpd Advisory ID RHSA-1999:041-03 Issue Date 1999-10-17 Updated on 1999-10-25 Keywords lpr lpd permissions Cross references N/A Revision History: 1999-10-25: New packages, to fix problems introduced by the security fix. 1999-10-19: New packages, to fix a remote printing bug. Add note about local printing fix for Red Hat Linux 6.1. 1. Topic: There are potential problems with file access checking in the lpr and lpd programs. These could allow users to potentially print files they do not have access to. Also, there are bugs in remote printing in the lpd that shipped with Red Hat Linux 6.1. 2. Problem description: There are two problems in the lpr and lpd programs. By exploiting a race between the access check and the actual file opening, it is potentially possible to have lpr read a file as root that the user does not have access to. Also, the lpd program would blindly open queue files as root; by use of the '-s' flag to lpr, it was possible to have lpd print files that the user could not access. Thanks go to Tymm Twillman for pointing out these vulnerabilities. (1999-10-19) Another problem with remote printing was fixed in lpr-0.44. If you are experiencing problems with remote printing in the previous errata update, it is recommended that you upgrade. There are no known security issues with the previous errata packages. If you are experiencing problems with local printingin Red Hat Linux 6.1, make sure that you have: alias parport_lowlevel parport_pc in your /etc/conf.modules file. (1999-10-25) The original security patch broke some aspects of printing. New errata RPMs are available which should fix the problem. 3. Bug IDs fixed: (see bugzilla for more information) 5122 5540 5697 5832 5835 5903 5949 4. Relevant releases/architectures: Red Hat Linux 6.1, all architectures 5. Obsoleted by: None 6. Conflicts with: None 7. RPMs required: Intel: lpr-0.46- 1.i386.rpm Alpha: lpr-0.46- 1.alpha.rpm SPARC: lpr-0.46- 1.sparc.rpm Source: lpr-0.46- 1.src.rpm Architecture neutral: 8. Solution: For each RPM for your particular architecture, run: rpm -Uvh filename where filename is the name of the RPM. 9. Verification: MD5 sum Package Name ------------------------------------------------------------------------- 03c996550636cbe4ca0a9fc853f969b6 lpr-0.46-1.src.rpm 30089f82ecf8e8a89565c5bba361697d lpr-0.46-1.alpha.rpm a01c0b9278c2c9ffb4bb6450703fc124 lpr-0.46-1.i386.rpm 41a1ef221a15446ed46b54092d7c14ca lpr-0.46-1.sparc.rpm These packages are GPG signed by Red Hat Inc. for security. Our key is available at: 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 10. References: . Concerns regarding file accessibility in lpr/lpd highlighted by Red Hat, crucial for safeguarding print functionalities. Bulletin RHSA-1999:041-03.. Red Hat Advisory, Lpr Security, File Access Issues, Remote Printing Flaws. . LinuxSecurity.com Team
Get the latest Linux and open source security news straight to your inbox.