-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: gpg,gpg2
Announcement ID: SUSE-SA:2006:075
Date: Wed, 13 Dec 2006 12:00:00 +0000
Affected Products: Novell Linux Desktop 9
Novell Linux POS 9
Open Enterprise Server
openSUSE 10.2
SUSE LINUX 10.1
SUSE LINUX 10.0
SUSE LINUX 9.3
SuSE Linux Desktop 1.0
SuSE Linux Enterprise Server 8
SuSE Linux Openexchange Server 4
SUSE LINUX Retail Solution 8
SuSE Linux School Server
SuSE Linux Standard Server 8
SUSE SLED 10
SUSE SLES 10
SUSE SLES 9
UnitedLinux 1.0
Vulnerability Type: remote code execution
Severity (1-10): 8
SUSE Default Package: yes
Cross-References: CVE-2006-6169, CVE-2006-6235
Content of This Advisory:
1) Security Vulnerability Resolved:
two security problems in GPG
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
Two security problems were fixed in the GNU Privacy Guard (GPG).
- Specially crafted files could overflow a buffer when gpg was used
in interactive mode (CVE-2006-6169).
- Specially crafted files could modify a function pointer and
could potentially execute code this way. (CVE-2006-6235).
Update for all SUSE Linux based products have been released.
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:
0032014cef28fd9d575ca9d56886dc9a
8cdf17f4928497c703df0986012bd924
SUSE LINUX 10.1:
714ad111277495f85fb4d75c07a436e1
df328ffaa0b0fa34e70932dd8eafd399
SUSE LINUX 10.0:
bbdac2ac9cf42f2e0744f93c7a27bd64
6b96bf0aa835b5c5a6d38f3fe9baa020
SUSE LINUX 9.3:
1f188d6e98593753dbf0115758c60700
493bb161ab9a0ee7e8b687da49fc874f
Power PC Platform:
openSUSE 10.2:
8ba71e773c0ed4bfad10017d4f0ad769
04e4aa189832a2834ac843d3d216b560
SUSE LINUX 10.1:
87d3e2efab5fda6d0c0fb0228e8089eb
9ecd1af3d67515388dc5f9c797d33fde
SUSE LINUX 10.0:
36dd086f17d69a2344387249f4f59828
0b0a3f42511f722f1113ceb2ddb1fe42
x86-64 Platform:
openSUSE 10.2:
178ec43c6b057b055e64fd8ce3b370f3
a480e34bc72c13902b060774a8c93614
SUSE LINUX 10.1:
424104d7e79aa13997a9cd5bf48daaed
f9813d58d65585d3216ce4a514288e60
SUSE LINUX 10.0:
542621ad20461324061e95d757f062a9
6e40568843721500e6e7a01e49478be5
SUSE LINUX 9.3:
d0857cd1ef3d71961e866f56c565b32d
20eb29a34cd71e5d1fa86bb53522a5ca
Sources:
openSUSE 10.2:
8b319a4138cc1ff4304dc45c369936c6
6ea5c120e635118233a97c5877ca10c0
SUSE LINUX 10.1:
551331ff3994d1e0a6a1c893f9d99c84
4dcf00273942790ccc8945f1badb441d
SUSE LINUX 10.0:
47425c0af8df3d11100bc938db0d9141
d76d488c78aa5c047f9d0d3a72bb1509
SUSE LINUX 9.3:
86c9afba71507f0d4f3f7e88fa599ea1
a911124ed914970d7c458caf03ddd709
Our maintenance customers are notified individually. The packages are
offered for installation from the maintenance web:
UnitedLinux 1.0
SuSE Linux Openexchange Server 4
Open Enterprise Server
Novell Linux POS 9
SuSE Linux Enterprise Server 8
SuSE Linux Standard Server 8
SuSE Linux School Server
SUSE LINUX Retail Solution 8
SuSE Linux Desktop 1.0
SUSE SLES 9
http://support.novell.com/techcenter/psdb/440643b5b7f99c513f043f911ca9d906.html
Novell Linux Desktop 9
SUSE SLES 10
SUSE SLED 10
http://support.novell.com/techcenter/psdb/440643b5b7f99c513f043f911ca9d906.html
http://support.novell.com/techcenter/psdb/d29d6e06422f5a6d9e87580b666bbb83.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.
====================================================================
