-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: samba
Announcement ID: SUSE-SA:2007:016
Date: Thu, 15 Feb 2007 15:00:00 +0000
Affected Products: SUSE LINUX 9.3
SUSE LINUX 10.0
SUSE LINUX 10.1
openSUSE 10.2
SUSE SLES 9
Novell Linux Desktop 9
Open Enterprise Server
Novell Linux POS 9
SUSE SLED 10
SUSE SLES 10
Vulnerability Type: remote denial of service
Severity (1-10): 5
SUSE Default Package: yes
Cross-References: CVE-2007-0452 CVE-2007-0453 CVE-2007-0454
Content of This Advisory:
1) Security Vulnerability Resolved:
samba remote denial of service
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
The Samba daemon was affected by a security problem, where a
logic error in the deferred open code can lead to an infinite loop
(CVE-2007-0452).
This problem could be used by remote authenticated attackers that
have access to the samba daemon.
Two other problems fixed in the upstream samba security release
that do not affect the SUSE Samba version:
- CVE-2007-0454: A format string problem in AFS ACL handling.
None of our shipping Samba versions have this option compiled in.
- CVE-2007-0453: A buffer overflow in nss_winbind on Solaris.
Linux is generally not affected by this problem.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
None.
4) Package Location and Checksums
The preferred method for installing security updates is to use the YaST
Online Update (YOU) tool. YOU detects which updates are required and
automatically performs the necessary steps to verify and install them.
Alternatively, download the update packages for your distribution manually
and verify their integrity by the methods listed in Section 6 of this
announcement. Then install the packages using the command
rpm -Fhv
to apply the update, replacing with the filename of the
downloaded RPM package.
x86 Platform:
openSUSE 10.2:
6b4cb2859d1321648fd46c30a6cfd343
b168ff8f07a792bf6fb66a91c893ae33
23e180e09af077fd64b35d8154d414c6
SUSE LINUX 10.1:
898c1eb0d0d4f1c806ce7fb8907753d7
d4f4efa7488aa12edd8f9ac2074fbbc3
f2d11fdea4fa460cfb5bda4e20fc5e86
SUSE LINUX 10.0:
ce7bcec67ee32a5415d4cb5907ec0372
SUSE LINUX 9.3:
7cc438d1cc0e8d4f479844bfccc8f698
Power PC Platform:
openSUSE 10.2:
d3b20aff8d493b48741b160c223bd268
790670189510dce128dca2f3f32f2b9c
43815e4efd08eae9e26242be281ba2fe
SUSE LINUX 10.1:
a2d2ce421081a74258c5328a5a432629
f86d3c623aadc34f1f64f173108f9c4b
b95e5643763b4f172adec030fa9033be
SUSE LINUX 10.0:
8badc1520efe79ac17b053be83648e46
x86-64 Platform:
openSUSE 10.2:
a23ee65e112c499b91af6c00ab068efa
09785d54c57f6da705acfa0f911b0b8d
c4b7be8c144842fd6947bfa7bf56891a
5a474e36e2f20b086138fb1d7a225942
c3ebad542ec53b71d3641310f796b430
1d0480ab089c3be84de54bc6bad71910
SUSE LINUX 10.1:
be6125ae205f2274150a29a4c251e8c0
6bd817cbdf52fd2e4ff8257442ba1d60
5cd72ad1de6b29173a9e3d23a1012b2c
a6509bd2aa7b9c7421e4d1777ce2bba3
0d3cb4f0c3bcef1a5569dd5d72b3c73b
e9dbf740b218735e385a348524d31108
SUSE LINUX 10.0:
f0ad5468ce42ff2631e9a6b3231010c1
SUSE LINUX 9.3:
fbd0c2a208fd91da991e53b54fb1a57d
Sources:
openSUSE 10.2:
54d62f5dad95981f0ae894619d0f06ea
SUSE LINUX 10.1:
8b2e1c4b662fc43fa03fe1ba60342c00
SUSE LINUX 10.0:
9217074c11c43c30860be28b33f034dd
SUSE LINUX 9.3:
117006e9e50e888e4848aa320e88b18d
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
SUSE SLES 10
http://support.novell.com/techcenter/psdb/1324cf66bf45968bebbd721ece5f92c7.html
SUSE SLED 10
http://support.novell.com/techcenter/psdb/1324cf66bf45968bebbd721ece5f92c7.html
Open Enterprise Server
http://support.novell.com/techcenter/psdb/75665d46b2b2dc409e252b880a1ad2f4.html
Novell Linux POS 9
http://support.novell.com/techcenter/psdb/75665d46b2b2dc409e252b880a1ad2f4.html
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/75665d46b2b2dc409e252b880a1ad2f4.html
SUSE SLES 9
http://support.novell.com/techcenter/psdb/75665d46b2b2dc409e252b880a1ad2f4.html
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
See SUSE Security Summary Report.
______________________________________________________________________________
6) Authenticity Verification and Additional Information
- Announcement authenticity verification:
SUSE security announcements are published via mailing lists and on Web
sites. The authenticity and integrity of a SUSE security announcement is
guaranteed by a cryptographic signature in each announcement. All SUSE
security announcements are published with a valid signature.
To verify the signature of the announcement, save it as text into a file
and run the command
gpg --verify
replacing with the name of the file where you saved the
announcement. The output for a valid signature looks like:
gpg: Signature made using RSA key ID 3D25D3D9
gpg: Good signature from "SuSE Security Team "
where is replaced by the date the document was signed.
If the security team's key is not contained in your key ring, you can
import it from the first installation CD. To import the key, use the
command
gpg --import gpg-pubkey-3d25d3d9-36e12d04.asc
- Package authenticity verification:
SUSE update packages are available on many mirror FTP servers all over the
world. While this service is considered valuable and important to the free
and open source software community, the authenticity and the integrity of
a package needs to be verified to ensure that it has not been tampered
with.
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) Using the internal gpg signatures of the rpm package
2) MD5 checksums as provided in this announcement
1) The internal rpm package signatures provide an easy way to verify the
authenticity of an RPM package. Use the command
rpm -v --checksig
to verify the signature of the package, replacing with the
filename of the RPM package downloaded. The package is unmodified if it
contains a valid signature from build@suse.de with the key ID 9C800ACA.
This key is automatically imported into the RPM database (on
RPMv4-based distributions) and the gpg key ring of 'root' during
installation. You can also find it on the first installation CD and at
the end of this announcement.
2) If you need an alternative means of verification, use the md5sum
command to verify the authenticity of the packages. Execute the command
md5sum
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
SUSE security announcement. Because the announcement containing the
checksums is cryptographically signed (by security@suse.de), the
checksums show proof of the authenticity of the package if the
signature of the announcement is valid. Note that the md5 sums
published in the SUSE Security Announcements are valid for the
respective packages only. Newer versions of these packages cannot be
verified.
- SUSE runs two security mailing lists to which any interested party may
subscribe:
opensuse-security@opensuse.org
- General Linux and SUSE security discussion.
All SUSE security announcements are sent to this list.
To subscribe, send an e-mail to
.
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 e-mail to
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
