Low: rsh security update
Advisory: 	RHSA-2005:074-10
Type: 	Security Advisory
Issued on: 	2005-05-18
Last updated on: 	2005-05-18
Affected Products: 	Red Hat Desktop (v. 3)
Red Hat Enterprise Linux AS (v. 3)
Red Hat Enterprise Linux ES (v. 3)
Red Hat Enterprise Linux WS (v. 3)
CVEs (cve.mitre.org): 	CAN-2004-0175

Details

Updated rsh packages that fix various bugs and a theoretical security issue
are now available.

This update has been rated as having low security impact by the Red Hat
Security Response Team

The rsh package contains a set of programs that allow users to run
commands on remote machines, login to other machines, and copy files
between machines, using the rsh, rlogin, and rcp commands. All three of
these commands use rhosts-style authentication.

The rcp protocol allows a server to instruct a client to write to arbitrary
files outside of the current directory. This could potentially cause a
security issue if a user uses rcp to copy files from a malicious server.
The Common Vulnerabilities and Exposures project (cve.mitre.org) has
assigned the name CAN-2004-0175 to this issue.

These updated packages also address the following bugs:

The rexec command failed with "Invalid Argument", because the code
used sigaction() as an unsupported signal.

The rlogind server reported "SIGCHLD set to SIG_IGN but calls wait()"
message to the system log because the original BSD code was ported
incorrectly to linux.

The rexecd server did not function on systems where client hostnames were
not in the DNS service, because server code called gethostbyaddr() for each
new connection.

The rcp command incorrectly used the "errno" variable and produced
erroneous error messages.

The rexecd command ignored settings in the /etc/security/limits file,
because the PAM session was incorrectly initialized.

The rexec command prompted for username and password regardless of the
~/.netrc configuration file contents. This updated package contains a patch
that no longer skips the ~/.netrc file.

All users of rsh should upgrade to these updated packages, which resolve
these issues.

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.

If up2date fails to connect to Red Hat Network due to SSL
Certificate Errors, you need to install a version of the
up2date client with an updated certificate. The latest version of
up2date is available from the Red Hat FTP site and may also be
downloaded directly from the RHN website:

https://rhn.redhat.com/help/latest-up2date.pxt

Updated packages
Red Hat Desktop (v. 3)
SRPMS:
rsh-0.17-17.6.src.rpm 	    9db33654428c9f2a68ae4fc3d3538b45
 
IA-32:
rsh-0.17-17.6.i386.rpm 	    d3c9d0998a481654e6aa70bae6d81284
rsh-server-0.17-17.6.i386.rpm 	    458e22f5bbb542402ff7f1d5b31d8efc
 
x86_64:
rsh-0.17-17.6.x86_64.rpm 	    d5a8b840af161bf40970e8d51b5be791
rsh-server-0.17-17.6.x86_64.rpm 	    bc656e79fc3002249f5eb17d4993f67b
 
Red Hat Enterprise Linux AS (v. 3)
SRPMS:
rsh-0.17-17.6.src.rpm 	    9db33654428c9f2a68ae4fc3d3538b45
 
IA-32:
rsh-0.17-17.6.i386.rpm 	    d3c9d0998a481654e6aa70bae6d81284
rsh-server-0.17-17.6.i386.rpm 	    458e22f5bbb542402ff7f1d5b31d8efc
 
IA-64:
rsh-0.17-17.6.ia64.rpm 	    0ef714b4988d67746492c7fcc94c6505
rsh-server-0.17-17.6.ia64.rpm 	    c5ffc16936049d313396840c1340b190
 
PPC:
rsh-0.17-17.6.ppc.rpm 	    b95b84629007515d08ebdb9dbfc3ef2f
rsh-server-0.17-17.6.ppc.rpm 	    fb95ecdabcdf4a94d3438d86c66fa10c
 
s390:
rsh-0.17-17.6.s390.rpm 	    3aeade4296a8fbef841988fa0931a627
rsh-server-0.17-17.6.s390.rpm 	    b974c6cfe31f0baa9863d543d4fbbc6c
 
s390x:
rsh-0.17-17.6.s390x.rpm 	    40007c9ed95ad284c2d6863bff54a69c
rsh-server-0.17-17.6.s390x.rpm 	    63df1e561f4ccd2d0a088e3c419e1647
 
x86_64:
rsh-0.17-17.6.x86_64.rpm 	    d5a8b840af161bf40970e8d51b5be791
rsh-server-0.17-17.6.x86_64.rpm 	    bc656e79fc3002249f5eb17d4993f67b
 
Red Hat Enterprise Linux ES (v. 3)
SRPMS:
rsh-0.17-17.6.src.rpm 	    9db33654428c9f2a68ae4fc3d3538b45
 
IA-32:
rsh-0.17-17.6.i386.rpm 	    d3c9d0998a481654e6aa70bae6d81284
rsh-server-0.17-17.6.i386.rpm 	    458e22f5bbb542402ff7f1d5b31d8efc
 
IA-64:
rsh-0.17-17.6.ia64.rpm 	    0ef714b4988d67746492c7fcc94c6505
rsh-server-0.17-17.6.ia64.rpm 	    c5ffc16936049d313396840c1340b190
 
x86_64:
rsh-0.17-17.6.x86_64.rpm 	    d5a8b840af161bf40970e8d51b5be791
rsh-server-0.17-17.6.x86_64.rpm 	    bc656e79fc3002249f5eb17d4993f67b
 
Red Hat Enterprise Linux WS (v. 3)
SRPMS:
rsh-0.17-17.6.src.rpm 	    9db33654428c9f2a68ae4fc3d3538b45
 
IA-32:
rsh-0.17-17.6.i386.rpm 	    d3c9d0998a481654e6aa70bae6d81284
rsh-server-0.17-17.6.i386.rpm 	    458e22f5bbb542402ff7f1d5b31d8efc
 
IA-64:
rsh-0.17-17.6.ia64.rpm 	    0ef714b4988d67746492c7fcc94c6505
rsh-server-0.17-17.6.ia64.rpm 	    c5ffc16936049d313396840c1340b190
 
x86_64:
rsh-0.17-17.6.x86_64.rpm 	    d5a8b840af161bf40970e8d51b5be791
rsh-server-0.17-17.6.x86_64.rpm 	    bc656e79fc3002249f5eb17d4993f67b
 
(The unlinked packages above are only available from the Red Hat Network)

Bugs fixed (see bugzilla for more information)

142094 - CAN-2004-1072 ia32el's binfmt_elf.c lacks recent security fix
145390 - RHEL4 U1 ia32el: new version expected from Intel
145400 - RHEL4 U1: ia32el cleanup glibc dependencies in spec file
145695 - IA64: Need SG_IO ioctl cmd support in execution layer

References
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0175

Keywords
rcp, rsh-server

These packages are GPG signed by Red Hat for security. Our key and details on how to verify the signature are available from:
https://www.redhat.com/security/team/key/#package

The Red Hat security contact is secalert@redhat.com. More contact details at http://www.redhat.com/security/team/contact/