-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: evolution
Announcement ID: SUSE-SA:2005:054
Date: Fri, 16 Sep 2005 13:00:00 +0000
Affected Products: Novell Linux Desktop 9
SUSE LINUX 9.2
SUSE LINUX 9.3
Vulnerability Type: remote code execution
Severity (1-10): 6
SUSE Default Package: yes
Cross-References: CAN-2005-2549, CAN-2005-2550
Content of This Advisory:
1) Security Vulnerability Resolved:
evolution format string bugs
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
Several format string bugs allowed remote attackers to cause
evolution to crash or even execute code via full vCard data, contact
data from remote LDAP servers, task list data from remote servers (CAN-2005-2549) or calendar entries (CAN-2005-2550).
2) Solution or Work-Around
There is no known workaround, please install the update packages.
3) Special Instructions and Notes
Please close and restart all running instances of evolution 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 9.3:
efce1fe443ee6ed166b54b1a5e3b98d5
40a63375e5251616fbc09eb60af677c0
d2402cf9eb95f22f4a51ef2649f16c85
3859e68fc6cb698320eb79eae81b4539
31492dd7d6e1b033adbd2bc6a3db2b9f
08122624504e8bd0e2761e1ca628ddb6
SUSE LINUX 9.2:
fdf65a48e6cbc5b6643c50c4eef5ae5a
5050f1a2f4291f0a5c6b6fdf12c1fe81
d64777fb32d0693af25d8e79e7fc9775
x86-64 Platform:
SuSE Linux 9.3:
7afad6527cf6975154de0d30954a089e
c986668e572836b02e8329d438fd366b
b8bd4014dbf302a1b1a87ebf5a0df0f3
b8104af8109a4d87cf90498af3fdc715
d17145cd0fcb2d54169a185a990c3c65
source rpm(s):
2fe71a8fd727fe03b7f6e1a3604b4528
e8fa87abca06e333bc6ceb16db771124
SuSE Linux 9.2:
ed6ab2108d1a2f7325f582455e2cec87
df0b35e88427feec0724857b9d6af05d
c7e60d7e67d51d89608da804c5d1b9cf
source rpm(s):
0365c61c839221763ff51d9594e5a765
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
https://www.suse.com:443/
______________________________________________________________________________
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.
====================================================================
