-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: evolution
Announcement ID: SUSE-SA:2008:014
Date: Fri, 14 Mar 2008 10:00:00 +0000
Affected Products: SUSE LINUX 10.1
openSUSE 10.2
openSUSE 10.3
Novell Linux Desktop 9
SUSE Linux Enterprise Desktop 10 SP1
SLE SDK 10 SP1
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2008-0072
Content of This Advisory:
1) Security Vulnerability Resolved:
format string vulnerability
Problem Description
2) Solution or Work-Around
3) Special Instructions and Notes
4) Package Location and Checksums
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
6) Authenticity Verification and Additional Information
______________________________________________________________________________
1) Problem Description and Brief Discussion
Evolution is a personal information manager (PIM) and workgroup information
management software.
The function emf_multipart_encrypted() that is used to process encrypted
messages is vulnerable to format-string bugs.
This bug can be abused by a remote attacker to execute arbitrary code by
sending a crafted encrypted eMail.
2) Solution or Work-Around
No work-around. Please install the current security update package.
3) Special Instructions and Notes
Please restart evolution.
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.3:
4a13b961952e7913af466ef1738c0196
2ecaf3f223841665df554aa8e20d5978
d06a664885565b04774d5d3c2afb84f5
openSUSE 10.2:
c7949a1af35d7abdb7a36fd7fc90607b
eadabc26ef71fbb91c498f202196e640
b8a8b80039aa8f1641c0103bb04f75a0
SUSE LINUX 10.1:
cc40ee93e3f2043a25dff22e62bc4e4e
b7fb5fec304a0e623be28233a66525ad
d2833e3948641af99a9e76026da6e8da
Power PC Platform:
openSUSE 10.3:
a6e9d56b825c7809bc62a87f546bdb50
772ce1adbb46a5ba5f703bf4dcfbd49e
946a9756bab858d4242736e055009173
openSUSE 10.2:
fa5ed56ee0d3a6718015bf722e34ff6f
91565615e83f40a40d435e9edcca2a63
443a51070cdb147473536fec3b704533
SUSE LINUX 10.1:
8b0beec2e2ecad7969fc91aa12c963d2
46706e204d46f01026af35b861c101a6
0c946a3533d2a55812f0fd60886e097f
x86-64 Platform:
openSUSE 10.3:
6c9f98241bf08edc4a77d52c4232ed60
bab5d0660dbb9076bd865ccae25bc68d
44778c1ea873e4e54021ce3588f406de
openSUSE 10.2:
8ac28a5b6875266d281400060867b45f
970d89a3ae7574334586a6b9388e1073
6ffb4564be38436e91a0b10b908ff18d
SUSE LINUX 10.1:
c352e53bfd35cb08ef87102829ed2dcb
a4d5259610db7850b39e2b4ae2b7a00e
50dae7030db765effccf36e23f112671
Sources:
openSUSE 10.3:
483dffff6981e43065de58916fc7faa0
openSUSE 10.2:
ba7d8312622f37c7d05dba4e6d03a5e0
SUSE LINUX 10.1:
93827395e2d05427ea717d882f444da5
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
Novell Linux Desktop 9
http://support.novell.com/techcenter/psdb/d93d20ddb38276f9b6f334240fd20e16.html
SLE SDK 10 SP1
http://support.novell.com/techcenter/psdb/d93d20ddb38276f9b6f334240fd20e16.html
SUSE Linux Enterprise Desktop 10 SP1
http://support.novell.com/techcenter/psdb/d93d20ddb38276f9b6f334240fd20e16.html
______________________________________________________________________________
5) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
______________________________________________________________________________
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
.
opensuse-security-announce@opensuse.org
- 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.
====================================================================
