-----BEGIN PGP SIGNED MESSAGE-----
______________________________________________________________________________
SUSE Security Announcement
Package: gtk2, gdk-pixbuf
Announcement ID: SUSE-SA:2005:065
Date: Wed, 16 Nov 2005 13:23:50 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SuSE Linux 9.0
SuSE Linux Desktop 1.0
SuSE Linux Enterprise Server 8
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2005-3186
CVE-2005-2976
CVE-2005-2975
Content of This Advisory:
1) Security Vulnerability Resolved:
- buffer overflow
- integer overflow
- infinite loop
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
The image loading library of the gdk-pixbug/gtk2 package is vulnerable
to several security-related bugs. This makes every application (mostly
GNOME applications) which is linked against this library vulnerable too.
A carefully crafted XPM file can be used to execute arbitrary code while
processing the image file. (CVE-2005-3186)
Additionally Ludwig Nussel from the SuSE Security-Team discovered an
integer overflow bug that can be used to execute arbitray code too
(CVE-2005-2976), and an infinite loop which leads to a denial-of-service
bug. (CVE-2005-2975)
2) Solution or Work-Around
none
3) Special Instructions and Notes
Please restart your system to make the update completely effective.
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.0:
0be068d079c58cbbaaa52e80820e6c6e
f6b37ad46fdd2ef2e7e2fc0e0e7598b1
a3ed5aec0eb8a110af839d91468d2790
c1981e12a87989d8ccab4d91418a6310
patch rpm(s):
f5fb1c48e841a15b4194f196bde2ff10
9e94e889694c900d46b02ef6c22ba5e4
64d3bee622ee73b5ac50dbf73e65f526
c431dc98c53e4b9a000822ab311e7b0a
source rpm(s):
f827e0f9da7d988d03098559119ac2d7
87e193dc3dce8969f47d6772e10b6e3a
SUSE Linux 9.3:
e7e6dceafe5a32ebab7a5b8a57661f87
9f4c9d44adb7756dc7c458f266da7420
b30948d644cc33444b5f03eeb3bca654
d515f01e0bb2292d647c04234b4c836a
patch rpm(s):
0439cde8222d72a9c1c46de79c609669
b9e5a1af3a8ad50879ae2339643b6953
42f9f1212c01aa7e866197f921646d79
da1f519c5e1b46cbf99a8eace632301f
source rpm(s):
6b7e57bea2b48ae3a7bfcc6378cdb7fe
d546d4e4ca0401b3d530f3263a83639d
SUSE Linux 9.2:
eea4e22113af4911766b88fb5afff990
f9bccebbdbc4951ba929c0b3bdd5e748
2f51e4f26ac2eb72ce9b188cf1a43d12
7f9d14be9e038b6079525a99141632c2
patch rpm(s):
3b9834d757ef903331eef11d263765aa
71a66acac5bdab4f540745e3f34513db
564c47762db1dfd0579a15a28a5bf198
ae58eb0eb9b21b6dc34a88576cda8d40
source rpm(s):
03fbda334b284e4764d287e635738e86
922628a980e0c30438381c8c75ba1681
SUSE Linux 9.1:
7076812e0edec87e47ac3e2773a29908
6dbc2a7c8ed993e6868ff9becd264e5b
cfd60a7867d3f19fdf2ef457ad61c3e2
0d9cd0869e0d461ca12f1b6702e09ae6
patch rpm(s):
c51455321b63c0f9db6b334879b74db2
2fdce6d74daaa4d0d36b9e299d005cf9
5d74d0c82efdf390e332e8cf51fe4018
953ab164ef73f95aa6eabf1b75fb9e81
source rpm(s):
7f25bb1592667d945298b55794a5ef34
3ea3a4213e98c872386be297b34dbe2f
SUSE Linux 9.0:
b7a34c4ca59ad4ff986539d41f5a3c62
45cfa2114c629d787f4c94ab7a7a26b5
2e1d762dbce602f2cd4bdba9c6481f22
70152ca0189e5af94730a39d362c4679
patch rpm(s):
92b162e49010fdd8bc01113a55f98963
43f931a74169a3ab25ca2219fad8e260
4736822d29064f7d05bee4f7eb877d5d
aace0a16af2c70132a5c7ce94ee9315d
source rpm(s):
54ea94d4fadeedc9617c6b9e3ab253c0
af97a34f1df9e537a5babb7309f10e85
x86-64 Platform:
SUSE Linux 10.0:
a6f11004299a6bc194758e58631eb14d
a6f11004299a6bc194758e58631eb14d
d10769dfd24dd41298930ba09bfef93f
d60b38927a4b25ff8d5c61b15805be4b
1e4281501647d4d227f6b2c7a6709e44
b1331a95be856bca8cc58a6ba92156fa
patch rpm(s):
57dae5b10043cef231709c75b9c1fef0
57dae5b10043cef231709c75b9c1fef0
0e1af403bc2a960a10b546b7551a83da
d496410edd7f6da4d48a4d8fbb71c6ae
969bb92ada0efac69c035ed71661deaf
f43a0a3ff732634d62ec5c0404a8883b
source rpm(s):
f827e0f9da7d988d03098559119ac2d7
87e193dc3dce8969f47d6772e10b6e3a
SUSE Linux 9.3:
270711bb1b6d023c9d3629f312e50749
37515e93536ea2937a0094e96aff080b
99822738b70178f12976c93f8bcc9e5e
7f083e788760599185f5383fbd6074cc
d07ea6f37ec3914951a4b32f085af0a0
7f083e788760599185f5383fbd6074cc
patch rpm(s):
831bcb2924eacdf3e06094f155366a64
5969ab9de490013c104d32070336c702
3f8bac290a7417022e4605681db0ec5f
fa40ceaa517c75d2029803f8910b528d
7d363a368b905f1f223cc6bb6a50a744
fa40ceaa517c75d2029803f8910b528d
source rpm(s):
6b7e57bea2b48ae3a7bfcc6378cdb7fe
2a749acae07d01e7249fc8348673e339
6b7e57bea2b48ae3a7bfcc6378cdb7fe
2a749acae07d01e7249fc8348673e339
d546d4e4ca0401b3d530f3263a83639d
2a749acae07d01e7249fc8348673e339
SUSE Linux 9.2:
2121161aa786e90f0e6ae4919da90a3a
3c3d9e1d3a02d7c53b6c9a453c9bbb79
de587bb88d05ef7ea69d61df65955cbb
5b3038697146b9fe3a736d6b0be689d6
dd99a4ce37d4504d17f89a5b835674c6
5b3038697146b9fe3a736d6b0be689d6
patch rpm(s):
aa15a4974bc6bb066829cf113c0470a9
f509872128353007b4ece66bfd839d6b
18f1afa7c3b873f8aecb9d93f273dca6
364d36b4a5a411054145ba41fb42b637
0a6ff2ebe95bedbfd200778e5e771d74
364d36b4a5a411054145ba41fb42b637
source rpm(s):
03fbda334b284e4764d287e635738e86
336ba61bad29df1bb83a51d940ce1347
03fbda334b284e4764d287e635738e86
336ba61bad29df1bb83a51d940ce1347
922628a980e0c30438381c8c75ba1681
336ba61bad29df1bb83a51d940ce1347
SUSE Linux 9.1:
dda27248ea4c5a9c1fac68296a02cda1
2e6c139ee38655ed850cf7392ec6147a
5f471e724c1e81511d282b2d5a0741da
05577700604c7651e0a9a4b0d34f929d
patch rpm(s):
c3495bec0ac4043dc7fb60112cd4b93e
1a0b8b30d9b5717aea242bab6cc04def
38523f56baf169bc35579869e77ea3cc
34ba091cf09bb721bbbe98194a7b8af7
source rpm(s):
c78f44a653b8c7078850214d6d0305a4
9d56df6bd1f836bff06f3c320e6af720
SUSE Linux 9.0:
1be59dd02108d53f2b6136970281458f
8c5a75f2e162f946120fbc1991177141
9db2ce9ac353de3b3d40baa694a265fc
c4dbed18cd259adc7069e4df1fb8925b
patch rpm(s):
99bcb3c24cdff9959c01e1f00a8bcd65
9ffaea29a6cb96579c158219db2fd8ea
5a684ec36f5f292aebccb55f7e23260d
f0c738175d874e0c2e29866a6ee87fcc
source rpm(s):
d8c2495842a49bfb178248df91c58464
fa3e8a1b1fb4b8fcc35cf9ea0afea3a3
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
https://www.suse.com:443/
https://www.suse.com:443/
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.
====================================================================
