____________________________________________________________________________
SuSE Security Announcement
Package: samba
Announcement-ID: SuSE-SA:2003:025
Date: Monday, Apr 7th 2003 21:00 MEST
Affected products: 7.1, 7.2, 7.3, 8.0, 8.1, 8.2
SuSE Linux Database Server,
SuSE eMail Server III, 3.1
SuSE Linux Enterprise Server 7, 8
SuSE Linux Firewall on CD/Admin host
SuSE Linux Connectivity Server
SuSE Linux Office Server
Vulnerability Type: remote root access
Severity (1-10): 7
SuSE default package: no
Cross References: CAN-2003-0201
Content of this advisory:
1) security vulnerability resolved: samba
problem description, discussion, solution and upgrade information
2) pending vulnerabilities, solutions, workarounds:
- glibc
- vnc
3) standard appendix (further information)
____________________________________________________________________________
1) problem description, brief discussion, solution, upgrade information
Digital Defense Inc. have discovered a buffer overflow in the samba
file server, the widely spread implementation of the SMB protocol.
The flaw allows a remote attacker to execute arbitrary commands as root
on a server that runs a vulnerable version of samba. The vulnerability
is known as DDI trans2.c overflow bug and is assigned the CVE ID
CAN-2003-0201. Since this vulnerability was found during an analysis of
an exploit happening in the wild, it should be assumed that exploits
are circulating in the internet.
A possible workaround is to restrict access using the "hosts allow"
directive in the smb.conf file to a group of trusted hosts/addresses
that should be able to access the server. Please see the sbm.conf(5)
manpage ("man smb.conf") for more details about such configuration
changes. It should be noted that each change of the configuration
requires restarting/reloading the samba daemon ("rcsmb reload").
The only efficient and permanent remedy for the vulnerability should
be to install the provided update packages from locations as listed
below.
It should be noted that this announcement is not a re-release of
SuSE Security Announcement SuSE-SA:2003:016. While the update packages
that are subject of this announcement (SuSE-SA:2003:025) also cover
the problems fixed with SuSE-SA:2003:016, it announces fixes for
a different vulnerability in addition. Therefore, the update packages
must be installed again.
Please note that the package names for SuSE products vary for different
products. There exist the following pairings:
server client
----------------------------
samba smbclnt
samba samba-client
samba-classic samba-classic-client
samba-ldap samba-ldap-client
To find out which packages are installed on your system, you may run
the following command:
rpm -qa|egrep '(samba|smbclnt)'
Please download the update package for your distribution and verify its
integrity by the methods listed in section 3) of this announcement.
Then, install the package using the command "rpm -Fhv file.rpm" to apply
the update.
Our maintenance customers are being notified individually. The packages
are being offered to install from the maintenance web.
SPECIAL INSTALL INSTRUCTIONS:
==============================
After successfully installing the update packages, you should restart
the samba server process(es) to make the changes in the system effective.
If you do not have a samba server running on your system, no further
action is required. If you have a samba server running, please run the
following command as root:
rcsmb try-restart
This will restart the samba daemon(s) if such daemon(s) are already
running.
Intel i386 Platform:
SuSE-8.2:
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.7a-72.i586.rpm
40d47bed1d286f77d61503d93b48e276
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-client-2.2.7a-72.i586.rpm
e6da6fc3da94548d8460f43193a493c9
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-2.2.7a-72.i586.patch.rpm
3105a12895ca956b4ab29c15dbfdc1d2
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/i586/samba-client-2.2.7a-72.i586.patch.rpm
d0418a25a2ea67c9577e23597a4c272d
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.2/rpm/src/samba-2.2.7a-72.src.rpm
3e8dc087f8574f3d1259e020d6c005a6
SuSE-8.1:
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.5-178.i586.rpm
684d7a7fff1f397736e3298d5a8c583d
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-client-2.2.5-178.i586.rpm
7d9d9da83c5b8e6f049a5eb9a36d05e2
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-2.2.5-178.i586.patch.rpm
905b3c3c4803457738aed00892d854bb
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/i586/samba-client-2.2.5-178.i586.patch.rpm
130d01b588d36576e1fbbce573a9bc86
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.1/rpm/src/samba-2.2.5-178.src.rpm
71b90b54594f9e392cd5dcd5d750496a
SuSE-8.0:
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/samba-2.2.3a-172.i386.rpm
a9ab49893027c3acd665e59ccecb6231
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/samba-client-2.2.3a-172.i386.rpm
4920d2f7edbf66b8196133469d32fd24
patch rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n2/samba-2.2.3a-172.i386.patch.rpm
bbde3c06e09d37def8f035161b8c932d
ftp://ftp.suse.com/pub/suse/i386/update/8.0/n1/samba-client-2.2.3a-172.i386.patch.rpm
70228df7686f1494fc44cbaa838720bf
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/8.0/zq1/samba-2.2.3a-172.src.rpm
eb8d2a7e6b8f43d19388f28afa1b9812
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n2/samba-2.2.1a-220.i386.rpm
965b260e660224d61c16ffb78a47fdfa
ftp://ftp.suse.com/pub/suse/i386/update/7.3/n1/samba-client-2.2.1a-220.i386.rpm
bf20ce9c220f9a939aa43e2445a2142e
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.3/zq1/samba-2.2.1a-220.src.rpm
bac7ada7dc2e3b5e238211fb181f4e32
SuSE-7.2:
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n2/samba-2.2.0a-52.i386.rpm
210da4fa4e1d601e78236d93e6abf5ac
ftp://ftp.suse.com/pub/suse/i386/update/7.2/n1/smbclnt-2.2.0a-52.i386.rpm
be819b970c2238a6d3c89e9f7f6dcb5f
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.2/zq1/samba-2.2.0a-52.src.rpm
b04e7eec150c1ba519605b522e1da25b
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n2/samba-2.0.10-32.i386.rpm
de27cbd77c32d2d29e77a518ca09c60d
ftp://ftp.suse.com/pub/suse/i386/update/7.1/n1/smbclnt-2.0.10-32.i386.rpm
b020a46952c87b61d66cbc38c340155e
source rpm(s):
ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/samba-2.0.10-32.src.rpm
45e6245a2fe47c430104671f41dc1a80
Sparc Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n2/samba-2.2.1a-76.sparc.rpm
2fa50186e7ff2ecb2f8ddebf2355efe4
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/n1/samba-client-2.2.1a-76.sparc.rpm
057d67ddd8fc56a82fe592dcb4928e7e
source rpm(s):
ftp://ftp.suse.com/pub/suse/sparc/update/7.3/zq1/samba-2.2.1a-76.src.rpm
7bcdd1c7a782f311292ca5214422fdc5
AXP Alpha Platform:
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n2/samba-2.0.10-23.alpha.rpm
6f88500a14ac86a6692788331b7aa626
ftp://ftp.suse.com/pub/suse/axp/update/7.1/n1/smbclnt-2.0.10-23.alpha.rpm
a4444318b224b42137f017c0840ecd0f
source rpm(s):
ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/samba-2.0.10-23.src.rpm
5c15b09bc46cb550a320575bc833daf5
PPC Power PC Platform:
SuSE-7.3:
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n2/samba-2.2.1a-150.ppc.rpm
5018c3418c8706a29e8f036eb006922f
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/n1/samba-client-2.2.1a-150.ppc.rpm
bd02b033055f87b5f4325e1a6bd4dca7
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.3/zq1/samba-2.2.1a-150.src.rpm
88c8a521103ae268843b951c0ca36669
SuSE-7.1:
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n2/samba-2.0.10-24.ppc.rpm
f78fe93753c2e230ab4c870bffe5a7f2
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/n1/smbclnt-2.0.10-24.ppc.rpm
17def1f1b5a3514252187a9a0b250bf9
source rpm(s):
ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/samba-2.0.10-24.src.rpm
926faf6542829ac64325965f18d1ba82
____________________________________________________________________________
2) Pending vulnerabilities in SuSE Distributions and Workarounds:
- glibc
New glibc packages will be available soon which fix a RPC XDR integer
overflow. The packages are currently being tested.
- vnc
VNC (Virtual Network Computing) uses a weak cookie generation process
which can be exploited by an attacker to bypass authentication.
New packages are currently being tested and will be available on our
FTP servers soon.
____________________________________________________________________________
3) standard appendix: authenticity verification, additional information
- Package authenticity verification:
SuSE update packages are available on many mirror ftp servers all over
the world. While this service is being considered valuable and important
to the free and open source software community, many users wish to be
sure about the origin of the package and its content before installing
the package. There are two verification methods that can be used
independently from each other to prove the authenticity of a downloaded
file or rpm package:
1) md5sums as provided in the (cryptographically signed) announcement.
2) using the internal gpg signatures of the rpm package.
1) execute the command
md5sum <name-of-the-file.rpm>
after you downloaded the file from a SuSE ftp server or its mirrors.
Then, compare the resulting md5sum with the one that is listed in the
announcement. Since the announcement containing the checksums is
cryptographically signed (usually using the key security@suse.de),
the checksums show proof of the authenticity of the package.
We disrecommend to subscribe to security lists which cause the
email message containing the announcement to be modified so that
the signature does not match after transport through the mailing
list software.
Downsides: You must be able to verify the authenticity of the
announcement in the first place. If RPM packages are being rebuilt
and a new version of a package is published on the ftp server, all
md5 sums for the files are useless.
2) rpm package signatures provide an easy way to verify the authenticity
of an rpm package. Use the command
rpm -v --checksig <file.rpm>
to verify the signature of the package, where <file.rpm> is the
filename of the rpm package that you have downloaded. Of course,
package authenticity verification can only target an un-installed rpm
package file.
Prerequisites:
a) gpg is installed
b) The package is signed using a certain key. The public part of this
key must be installed by the gpg program in the directory
~/.gnupg/ under the user's home directory who performs the
signature verification (usually root). You can import the key
that is used by SuSE in rpm packages for SuSE Linux by saving
this announcement to a file ("announcement.txt") and
running the command (do "su -" to be root):
gpg --batch; gpg < announcement.txt | gpg --import
SuSE Linux distributions version 7.1 and thereafter install the
key "build@suse.de" upon installation or upgrade, provided that
the package gpg is installed. The file containing the public key
is placed at the top-level directory of the first CD (pubring.gpg)
and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de .
- SuSE runs two security mailing lists to which any interested party may
subscribe:
suse-security@suse.com
- general/linux/SuSE security discussion.
All SuSE security announcements are sent to this list.
To subscribe, send an email to
<suse-security-subscribe@suse.com>.
suse-security-announce@suse.com
- SuSE's announce-only mailing list.
Only SuSE's security announcements are sent to this list.
To subscribe, send an email to
<suse-security-announce-subscribe@suse.com>.
For general information or the frequently asked questions (faq)
send mail to:
<suse-security-info@suse.com> or
<suse-security-faq@suse.com> respectively.
=====================================================================
SuSE's security contact is <security@suse.com> or <security@suse.de>.
The <security@suse.de> public key is listed below.
=====================================================================
____________________________________________________________________________
The information in this advisory may be distributed or reproduced,
provided that the advisory is not modified in any way. In particular,
it is desired that the clear-text signature shows proof of the
authenticity of the text.
SuSE Linux AG makes no warranties of any kind whatsoever with respect
to the information contained in this security advisory.
Type Bits/KeyID Date User ID
pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security@suse.de>
pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build@suse.de>
Roman Drahtmüller,
SuSE Security.
- --
- -
| Roman Drahtmüller <draht@suse.de> // "You don't need eyes to see, |
SuSE Linux AG - Security Phone: // you need vision!"
| Nürnberg, Germany +49-911-740530 // Maxi Jazz, Faithless |
- -
-------------------------------------------------------------------------
[slackware-security] Samba security problem fixed
The samba packages in Slackware 8.1 and 9.0 have been upgraded to
Samba 2.2.8a to fix a security problem.
All sites running samba should upgrade.
Here are the details from the Slackware 9.0 ChangeLog:
+--------------------------+
Mon Apr 7 14:26:53 PDT 2003
patches/packages/samba-2.2.8a-i386-1.tgz: Upgraded to samba-2.2.8a.
From the samba-2.2.8a WHATSNEW.txt:
****************************************
* IMPORTANT: Security bugfix for Samba *
****************************************
Digital Defense, Inc. has alerted the Samba Team to a serious
vulnerability in all stable versions of Samba currently shipping.
The Common Vulnerabilities and Exposures (CVE) project has assigned
the ID CAN-2003-0201 to this defect.
This vulnerability, if exploited correctly, leads to an anonymous
user gaining root access on a Samba serving system. All versions
of Samba up to and including Samba 2.2.8 are vulnerable. An active
exploit of the bug has been reported in the wild. Alpha versions of
Samba 3.0 and above are NOT vulnerable.
(* Security fix *)
+--------------------------+
More information may be found in the Samba 2.2.8a release notes.
WHERE TO FIND THE NEW PACKAGES:
+-----------------------------+
Updated Samba package for Slackware 8.1:
ftp://ftp.slackware.com/pub/slackware/slackware-8.1/patches/packages/samba-2.2.8a-i386-1.tgz
Updated Samba package for Slackware 9.0:
ftp://ftp.slackware.com/pub/slackware/slackware-9.0/patches/packages/samba-2.2.8a-i386-1.tgz
MD5 SIGNATURES:
+-------------+
Here are the md5sums for the packages:
Slackware 8.1 package:
875ef129196f56d71c833911f3156cd5 samba-2.2.8a-i386-1.tgz/
Slackware 9.0 package:
d1d2b689b79a1a8dfc0ee34fd390e72c samba-2.2.8a-i386-1.tgz/
INSTALLATION INSTRUCTIONS:
+------------------------+
As root, stop the samba server:
. /etc/rc.d/rc.samba stop
Next, upgrade the samba package(s) with upgradepkg:
upgradepkg samba-2.2.8a-i386-1.tgz/
Finally, start samba again:
. /etc/rc.d/rc.samba start
+-----+
Slackware Linux Security Team
http://slackware.com/gpg-key
security@slackware.com
---------------------------------------------------------------------
Red Hat Security Advisory
Synopsis: New samba packages fix security vulnerability
Advisory ID: RHSA-2003:137-01
Issue date: 2003-04-08
Updated on: 2003-04-08
Product: Red Hat Linux
Keywords: smb
Cross references:
Obsoletes: RHSA-2003:095
CVE Names: CAN-2003-0196 CAN-2003-0201
---------------------------------------------------------------------
1. Topic:
Updated Samba packages that fix a security vulnerability are now available
for Red Hat Linux 7.2, 7.3, 8.0, and 9. Packages for Red Hat Linux 7.1
will be added shortly.
2. Relevant releases/architectures:
Red Hat Linux 7.2 - i386, ia64
Red Hat Linux 7.3 - i386
Red Hat Linux 8.0 - i386
Red Hat Linux 9 - i386
3. Problem description:
Samba is a suite of utilities which provide file and printer sharing
services to SMB/CIFS clients.
A security vulnerability has been found in versions of Samba up to and
including 2.2.8. An anonymous user could exploit the vulnerability to
gain root access on the target machine. Note that this is a different
vulnerability than the one fixed by RHSA-2003:095.
An exploit for this vulnerability is publicly available.
All users of Samba are advised to update to the packages listed in this
erratum, which contain a backported patch correcting this vulnerability.
4. 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.
5. Bug IDs fixed (http://bugzilla.redhat.com/bugzilla for more info):
86307 - Netlogon causes DoS since upgrade to latest update
82041 - ignores wide links, serving files which shouldn't be served
6. RPMs required:
Red Hat Linux 7.2:
SRPMS:
ftp://updates.redhat.com/7.2/en/os/SRPMS/samba-2.2.7-3.7.2.src.rpm
i386:
ftp://updates.redhat.com/7.2/en/os/i386/samba-2.2.7-3.7.2.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/samba-common-2.2.7-3.7.2.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/samba-client-2.2.7-3.7.2.i386.rpm
ftp://updates.redhat.com/7.2/en/os/i386/samba-swat-2.2.7-3.7.2.i386.rpm
ia64:
ftp://updates.redhat.com/7.2/en/os/ia64/samba-2.2.7-3.7.2.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/samba-common-2.2.7-3.7.2.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/samba-client-2.2.7-3.7.2.ia64.rpm
ftp://updates.redhat.com/7.2/en/os/ia64/samba-swat-2.2.7-3.7.2.ia64.rpm
Red Hat Linux 7.3:
SRPMS:
ftp://updates.redhat.com/7.3/en/os/SRPMS/samba-2.2.7-3.7.3.src.rpm
i386:
ftp://updates.redhat.com/7.3/en/os/i386/samba-2.2.7-3.7.3.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/samba-common-2.2.7-3.7.3.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/samba-client-2.2.7-3.7.3.i386.rpm
ftp://updates.redhat.com/7.3/en/os/i386/samba-swat-2.2.7-3.7.3.i386.rpm
Red Hat Linux 8.0:
SRPMS:
ftp://updates.redhat.com/8.0/en/os/SRPMS/samba-2.2.7-5.8.0.src.rpm
i386:
ftp://updates.redhat.com/8.0/en/os/i386/samba-2.2.7-5.8.0.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/samba-common-2.2.7-5.8.0.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/samba-client-2.2.7-5.8.0.i386.rpm
ftp://updates.redhat.com/8.0/en/os/i386/samba-swat-2.2.7-5.8.0.i386.rpm
Red Hat Linux 9:
SRPMS:
ftp://updates.redhat.com/9/en/os/SRPMS/samba-2.2.7a-8.9.0.src.rpm
i386:
ftp://updates.redhat.com/9/en/os/i386/samba-2.2.7a-8.9.0.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/samba-common-2.2.7a-8.9.0.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/samba-client-2.2.7a-8.9.0.i386.rpm
ftp://updates.redhat.com/9/en/os/i386/samba-swat-2.2.7a-8.9.0.i386.rpm
7. Verification:
MD5 sum Package Name
--------------------------------------------------------------------------
4753f8b50da25cd251354248cc309930 7.2/en/os/SRPMS/samba-2.2.7-3.7.2.src.rpm
9047e4072c65e9f11bbfbb00e45ee257 7.2/en/os/i386/samba-2.2.7-3.7.2.i386.rpm
df7f4ba09d0ead29e1e06b8467b30935 7.2/en/os/i386/samba-client-2.2.7-3.7.2.i386.rpm
d035f89b5155099232eb1d12e3b551ef 7.2/en/os/i386/samba-common-2.2.7-3.7.2.i386.rpm
7c852414dc27505e6cad198d1059580a 7.2/en/os/i386/samba-swat-2.2.7-3.7.2.i386.rpm
208fc22f66c028014ee590fd4b09cd8f 7.2/en/os/ia64/samba-2.2.7-3.7.2.ia64.rpm
f4cc93943361cd213269e1ba40da0b18 7.2/en/os/ia64/samba-client-2.2.7-3.7.2.ia64.rpm
d333b4149ef242d6c4059f45f462219d 7.2/en/os/ia64/samba-common-2.2.7-3.7.2.ia64.rpm
d7116e4dc29f5ca4de4cf97c4bb945bb 7.2/en/os/ia64/samba-swat-2.2.7-3.7.2.ia64.rpm
0fd8526d3a8f5e441bc16098e124b285 7.3/en/os/SRPMS/samba-2.2.7-3.7.3.src.rpm
edbd81c52155a0b7eb107fda054ca945 7.3/en/os/i386/samba-2.2.7-3.7.3.i386.rpm
7c03367ed0576d580a60df18d97c6681 7.3/en/os/i386/samba-client-2.2.7-3.7.3.i386.rpm
689ca3fed3b63d59d680109881c610bb 7.3/en/os/i386/samba-common-2.2.7-3.7.3.i386.rpm
343902163244399713a77161c8cc58f5 7.3/en/os/i386/samba-swat-2.2.7-3.7.3.i386.rpm
2198081f27c842f66377c9b595b4694d 8.0/en/os/SRPMS/samba-2.2.7-5.8.0.src.rpm
2fea298375c9f6307e84dc384c97c63c 8.0/en/os/i386/samba-2.2.7-5.8.0.i386.rpm
559490c7bddce43b98c4a65cfdc03e29 8.0/en/os/i386/samba-client-2.2.7-5.8.0.i386.rpm
0c20656f0202f421bf8ae536d1347a98 8.0/en/os/i386/samba-common-2.2.7-5.8.0.i386.rpm
0c0542bdd2f787b72e440af66927f9f1 8.0/en/os/i386/samba-swat-2.2.7-5.8.0.i386.rpm
9e1763f38f616b76030584eea6e4bbaf 9/en/os/SRPMS/samba-2.2.7a-8.9.0.src.rpm
4fca0fbb65534abf85972deb9bfed4bc 9/en/os/i386/samba-2.2.7a-8.9.0.i386.rpm
9e40436148d54048e22670787a66a92e 9/en/os/i386/samba-client-2.2.7a-8.9.0.i386.rpm
ef0c8e03cd63888283e58e4b9e5a84fb 9/en/os/i386/samba-common-2.2.7a-8.9.0.i386.rpm
23277324eca8438aa7c4ae67ea4f7594 9/en/os/i386/samba-swat-2.2.7a-8.9.0.i386.rpm
These packages are GPG signed by Red Hat for security. Our key is
available at http://www.redhat.com/solutions/security/news/publickey/
You can verify each package with the following command:
rpm --checksig -v <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:
md5sum <filename>
8. References:
http://www.digitaldefense.net/labs/advisories/DDI-1013.txt
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0196
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2003-0201
9. Contact:
The Red Hat security contact is <security@redhat.com>. More contact
details at http://www.redhat.com/solutions/security/news/contact/
Copyright 2003 Red Hat, Inc.
- --------------------------------------------------------------------------
Trustix Secure Linux Security Advisory #2003-0019
Package name: samba
Summary: Remote root exploit
Date: 2003-04-07
Affected versions: TSL 1.2, 1.5
- --------------------------------------------------------------------------
Package description:
Samba provides an SMB server which can be used to provide network
services to SMB (sometimes called "Lan Manager") clients, including
various versions of MS Windows, OS/2, and other Linux machines. Samba
uses NetBIOS over TCP/IP (NetBT) protocols and does NOT need NetBEUI
(Microsoft Raw NetBIOS frame) protocol.
Problem description:
A buffer overflow has been discovered in Samba affecting all versions
prior to 2.2.8a allowing for a remote root compromise. An exploit
has been released to the wild. This release patches our 2.2.8 package
up to 2.2.8a.
Action:
We recommend that all systems with this package installed be upgraded.
Please note that if you do not need the functionality provided by this
package, you may want to remove it from your system.
Location:
All TSL updates are available from
<URI:http://www.trustix.net/pub/Trustix/updates/>;
<URI:ftp://ftp.trustix.net/pub/Trustix/updates/>
About Trustix Secure Linux:
Trustix Secure Linux is a small Linux distribution for servers. With focus
on security and stability, the system is painlessly kept safe and up to
date from day one using swup, the automated software updater.
Automatic updates:
Users of the SWUP tool can enjoy having updates automatically
installed using 'swup --upgrade'.
Get SWUP from:
<URI:ftp://ftp.trustix.net/pub/Trustix/software/swup/>
Public testing:
These packages have been available for public testing for some time.
If you want to contribute by testing the various packages in the
testing tree, please feel free to share your findings on the
tsl-discuss mailinglist.
The testing tree is located at
<URI:http://www.trustix.net/pub/Trustix/testing/>;
<URI:ftp://ftp.trustix.net/pub/Trustix/testing/>
Questions?
Check out our mailing lists:
<URI:http://www.trustix.net/support/>;
Verification:
This advisory along with all TSL packages are signed with the TSL sign key.
This key is available from:
<URI:http://www.trustix.net/TSL-GPG-KEY>;
The advisory itself is available from the errata pages at
<URI:http://www.trustix.net/errata/trustix-1.2/>; and
<URI:http://www.trustix.net/errata/trustix-1.5/>;
or directly at
<URI:http://www.trustix.net/errata/misc/2003/TSL-2003-0019-samba.asc.txt>;
MD5sums of the packages:
- --------------------------------------------------------------------------
70a3e32471a42ce18f34213e1a9ef915 ./1.2/RPMS/samba-2.2.8-3tr.i586.rpm
98ea77c8f443e601cea3ac951fbd94d3 ./1.2/RPMS/samba-client-2.2.8-3tr.i586.rpm
ec368177237dcdd3cb7295d849c93842 ./1.2/RPMS/samba-common-2.2.8-3tr.i586.rpm
b6b7ace9c530cdc058dddc04328502b1 ./1.2/SRPMS/samba-2.2.8-3tr.src.rpm
de491c36d57f5009e21954e81627fbc0 ./1.5/RPMS/samba-2.2.8-3tr.i586.rpm
21ec051f00d60ff915605d8140e41f3f ./1.5/RPMS/samba-client-2.2.8-3tr.i586.rpm
53a2d161d258fc6e37facf05a859ac69 ./1.5/RPMS/samba-common-2.2.8-3tr.i586.rpm
b6b7ace9c530cdc058dddc04328502b1 ./1.5/SRPMS/samba-2.2.8-3tr.src.rpm
- --------------------------------------------------------------------------
Trustix Security Team
Samba Security Advisories: SuSE, Slackware, Red Hat, Trustix
By
Get the Free Newsletter!
Subscribe to Developer Insider for top news, trends, & analysis