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

4. Obsoleted by:
None

5. Conflicts with:
The smbmount code shipped with Samba 2.0 is only 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 smbmount 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

The samba package shipped with Red Hat Linux 6.0 (samba-2.0.3-8) has an erroneous post-uninstall script. If this package is upgraded to the errata release, it could cause /var/log/samba and /var/lock/samba to be missing. It is recommended that users of samba under Red Hat Linux 6.0 uninstall the previous release using 'rpm -e samba' before installing the errata release.

6. RPMs required:

Intel:

ftp://updates.Red Hat.com/6.0/i386/

samba- 2.0.5a-1.i386.rpm
samba-client-2.0.5a-1.i386.rpm

Alpha:

ftp://updates.Red Hat.com/6.0/alpha/

samba- 2.0.5a-1.alpha.rpm
samba-client-2.0.5a-1.alpha.rpm

SPARC:

ftp://updates.Red Hat.com/6.0/sparc/

samba- 2.0.5a-1.sparc.rpm
samba-client-2.0.5a-1.sparc.rpm

Source:

ftp://updates.Red Hat.com/6.0/SRPMS

samba- 2.0.5a-1.src.rpm

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 (okir@caldera.de) for discovering the security holes, as well as the Samba team.

8. Solution:
Install the updated RPMs, and restart the affected services by running:

For each RPM for your particular architecture:

rpm -Uvh filename

where filename is the name of the RPM.

Then run:

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

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







 

You can verify each package with the following command: rpm --checksig

If you only wish to verify that each package has not been corrupted o tampered with, examine only the md5sum with the following command: rpm --checksig --nopgp

10. References:
<19990721023513Z12865037-4222+1570@samba.anu.edu.au>