-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: cron
Announcement ID: SUSE-SA:2006:027
Date: Wed, 31 May 2006 15:00:00 +0000
Affected Products: SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SuSE Linux Desktop 1.0
SuSE Linux Enterprise Server 8
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: local privilege escalation
Severity (1-10): 7
SUSE Default Package: yes
Cross-References: CVE-2006-2607
Content of This Advisory:
1) Security Vulnerability Resolved:
local privilege escalation using cron
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
Vixie Cron is the default CRON daemon in all SUSE Linux based
distributions.
The code in do_command.c in Vixie cron does not check the return code
of a setuid call, which might allow local users to gain root privileges
if setuid fails in cases such as PAM failures or resource limits.
This problem is known to affect only distributions with Linux 2.6
kernels, but the package was updated for all distributions for
completeness.
This problem is tracked by the Mitre CVE ID CVE-2006-2607.
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please restart cron after the update.
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:
SUSE LINUX 10.1:
e497e8d493f1b94c0891af1026be4d0a
SUSE LINUX 10.0:
a7daa9be8f6d1f3d5b87904e934ee235
SUSE LINUX 9.3:
feabbd699c9504dc4cf0bf0ba91e6f2d
SUSE LINUX 9.2:
0979cea40c43166044c66364b148101b
SUSE LINUX 9.1:
e140f798e6146f52ca2621a6ef678a45
Power PC Platform:
SUSE LINUX 10.1:
0b0550667503fc422ae7601b4cb513e6
SUSE LINUX 10.0:
711aeec2e8bfcb02835478e3c5bc62c8
x86-64 Platform:
SUSE LINUX 10.1:
01885af8563e8f2e093b7741e0e7ee95
SUSE LINUX 10.0:
3716db1e6d608fc4714b8ac137c94059
SUSE LINUX 9.3:
4287461b019ece311e32082fd87bc0a9
SUSE LINUX 9.2:
574294ae7f583add41bd45774988cb4e
SUSE LINUX 9.1:
6b26840c02592f7978d841f99743371d
Sources:
SUSE LINUX 10.1:
f43d85f87f2571b7a72c580f40027abd
SUSE LINUX 10.0:
78ea0581677076016e90b109e6154b12
SUSE LINUX 9.3:
9a1b7e7f96f6daaa2ce77f922ff9df9a
SUSE LINUX 9.2:
26adb41a9c1beb796184323a0c0fed8a
SUSE LINUX 9.1:
84e82588b2fcd45ff23e02502acbc8d2
c0aa0ac7fb31ae24da6404b0e0cdc218
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
UnitedLinux 1.0
SUSE SLES 9
SuSE Linux Desktop 1.0
SuSE Linux Enterprise Server 8
______________________________________________________________________________
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:
suse-security@suse.com
- 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
.
For general information or the frequently asked questions (FAQ),
send mail to or
.
==================================================================== SUSE's security contact is or .
The public key is listed below.
====================================================================
