Red Hat Security Advisory: New Samba packages available

Date: Thu, 22 Jul 1999 15:06:09 -0400
From: Bill Nottingham @redhat.com
To: [email protected]

                   Red Hat, Inc. Security Advisory

Synopsis:               New Samba packages for Red Hat Linux 4.2, 5.2, 6.0
Advisory ID:            RHSA-1999:022-01
Issue date:             1999-07-22
Updated on:             
Keywords:               samba smbd nmbd security
Cross references:       

1. Topic:

Samba 2.0.5a has been released. Among the fixes in this release
are several security issues present in previous Samba releases.

2. Bug IDs fixed:

1321 2557 2625 2779 2923 2982 3715

3. Relevant releases/architectures:

Red Hat Linux 6.0, all architectures

Red Hat Linux 5.2, all architectures

Red Hat Linux 4.2, all architectures

4. Obsoleted by:

5. Conflicts with:

The smbmount code shipped with Samba 2.0 is not compatible
with the Linux 2.2 kernel, so it has not been built for
the Red Hat Linux 4.2 and 5.2 releases. If support for
the 2.2 kernel is needed under Red Hat Linux 4.2 or 5.2,
the source RPM can be rebuilt with the following command line
(RPM version 3.0 is required):

rpm --define "KERN22 yes" --rebuild samba-2.0.5a-.src.rpm

6. RPMs required:

Red Hat Linux 6.0:

Intel: ftp://updates.redhat.com/6.0/i386/

Alpha: ftp://updates.redhat.com/6.0/alpha/

Sparc: ftp://updates.redhat.com/6.0/sparc/

Source: ftp://updates.redhat.com/6.0/

Red Hat Linux 5.2:

Intel: ftp://updates.redhat.com/5.2/i386/

Alpha: ftp://updates.redhat.com/5.2/alpha/

Sparc: ftp://updates.redhat.com/5.2/sparc/

Source: ftp://updates.redhat.com/5.2/

Red Hat Linux 4.2:

Intel: ftp://updates.redhat.com/4.2/i386/

Alpha: ftp://updates.redhat.com/4.2/alpha/

Sparc: ftp://updates.redhat.com/4.2/sparc/

Source: ftp://updates.redhat.com/4.2/

7. Problem description:

Several security issues were present in earlier samba releases.
- a denial-of-service attack could be performed against nmbd.
- a buffer overflow was present in the message service in smbd
  (not enabled by default under Red Hat Linux)
- a race condition was present in smbmnt that could cause problems
  if installed setuid root (it is not installed setuid root by
  default under Red Hat Linux 6.0, and is not present under Red
  Hat Linux 4.2 or 5.2)

Thanks go to Olaf Kirch ([email protected]) for discovering the
security holes, as well as the Samba team.

8. Solution:

Install the updated RPMs, and restart the affected services by

/etc/rc.d/init.d/smb restart

For each RPM for your particular architecture, run:
rpm -Uvh 
where filename is the name of the RPM.

9. Verification:

MD5 sum                           Package Name
5167d97fb2f0949991555a3b8e86d509  samba-2.0.5a-1.i386.rpm
969d609925bc09f9c113907124828dc6  samba-client-2.0.5a-1.i386.rpm
d8091f3fa0aeda8febf3553d5b92f53f  samba-2.0.5a-1.alpha.rpm
99f334ef87347877d1b79d4801044547  samba-client-2.0.5a-1.alpha.rpm
58b1afe4c81028435e6cad1325d4bbee  samba-2.0.5a-1.sparc.rpm
6e3939fcebba7ace639b766b1cf36cab  samba-client-2.0.5a-1.sparc.rpm
5c87d78148a8a224e5f89e5dce9af1ae  samba-2.0.5a-1.src.rpm

6ce227464edc1e79cf4433ede6d18c05  samba-2.0.5a-0.5.2.i386.rpm
0f8d4c9606af2fd809c55a6dd3f9beae  samba-client-2.0.5a-0.5.2.i386.rpm
cb51e889747ed1786996323863f64868  samba-2.0.5a-0.5.2.alpha.rpm
f82cfb4807fa9399005a03d6dd65dca5  samba-client-2.0.5a-0.5.2.alpha.rpm
d56551d53be6928556bb58517f265e9f  samba-2.0.5a-0.5.2.sparc.rpm
371f7de9553d9c86c4b62d2a92c84bf0  samba-client-2.0.5a-0.5.2.sparc.rpm
e411e3c19d19ab89d35e834c7d379589  samba-2.0.5a-0.5.2.src.rpm

c5d267fc6b47a84f0571f0ce1a7a15aa  samba-2.0.5a-0.4.2.i386.rpm
3d07e39245cdc5d8aa0ba8d50e6178f1  samba-client-2.0.5a-0.4.2.i386.rpm
f3db3e6f607afbd861610570154fd19d  samba-2.0.5a-0.4.2.alpha.rpm
7972cf576734d1b006258a8ca02c80ff  samba-client-2.0.5a-0.4.2.alpha.rpm
c44a4c13f171f31686d91da3b8370311  samba-2.0.5a-0.4.2.sparc.rpm
a6c235a206349e347dfe35ac0064d901  samba-client-2.0.5a-0.4.2.sparc.rpm
0c326cb2a2b0964026d286fb5f6b8079  samba-2.0.5a-0.4.2.src.rpm

These packages are PGP signed by Red Hat Inc. for security.  Our key
is available at:
You can verify each package with the following command:
rpm --checksig  
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 --nopgp 

10. References:
        <[email protected]>


Please refer to the information about this list as well as general
information about Linux security at http://www.aoy.com/Linux/Security.