Vulnerability Assessment & Network Security Forums

If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important.  If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.

Home >> Browse Vulnerability Assessment Database >> Red Hat Local Security Checks >> RHSA-2002-120: LPRng

Vulnerability Assessment Details

RHSA-2002-120: LPRng

Vulnerability Assessment Summary
Check for the version of the LPRng packages

Detailed Explanation for this Vulnerability Assessment

The LPRng print spooler, as shipped in Red Hat Linux Advanced Server 2.1,
accepts all remote print jobs by default. Updated LPRng packages are
available to fix this issue.

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

The Common Vulnerabilities and Exposures project ( has
assigned the name CVE-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.

Please note that default installations of Red Hat Linux Advanced Server 2.1
include ipchains rules blocking remote access to the print spooler IP port

as a result those installations already reject remote job submissions.

NOTE: There are special instructions for installing this update at
the end of the "Solution" section.

Solution :
Network Security Threat Level: High

Networks Security ID:

Vulnerability Assessment Copyright: This script is Copyright (C) 2004 Tenable Network Security

Cables, Connectors


No Discussions have been posted on this vulnerability.