-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
______________________________________________________________________________
SUSE Security Announcement
Package: ipsec-tools,freeswan,openswan
Announcement ID: SUSE-SA:2005:070
Date: Tue, 20 Dec 2005 11:00:00 +0000
Affected Products: SUSE LINUX 10.0
SUSE LINUX 9.3
SUSE LINUX 9.2
SUSE LINUX 9.1
SUSE Linux Enterprise Server 9
Vulnerability Type: remote denial of service
Severity (1-10): 5
SUSE Default Package: no
Cross-References: CVE-2005-3671, CVE-2005-3732
Content of This Advisory:
1) Security Vulnerability Resolved:
Internet Key Exchange v1 problems in various IPsec implementations
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
Openswan, Freeswan and raccoon (ipsec-tools) have been updated to fix
crashes in aggressive mode. An attacker might send specially crafted
packets that can crash racoon or Pluto.
The ipsec-tools / racoon crashes are tracked by the Mitre CVE ID
CVE-2005-3732.
The openswan / freeswan crashes are tracked by the Mitre CVE ID
CVE-2005-3671.
SUSE Linux Enterprise Server 8 and SUSE Linux 9.0 contain freeswan
1.x and seem no to be affected by this problem.
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 openswan, freeswan
or racoon 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.0:
f82b5941ca8143a7f81315f2309c28e9
9d2318b4da837ae3175547ba261235c5
SUSE LINUX 9.3:
57b586b7aaa612c6250a8b037afe9335
6c152ba37641677fc4c59c44199a9225
SUSE LINUX 9.2:
ca1ffa39b311744976bc9754f003c71f
88dedfd8ad12456158b0f60d0a4714f4
SUSE LINUX 9.1:
64b2fc324586f4af0060b8dd0c6597eb
c523ed28073d5d76a1468763cc3820ea
Power PC Platform:
SUSE LINUX 10.0:
fc12c770db47d6a51b7cfc7e92b0f003
6a0c80ce5f3a489221e605ea7ee724d5
x86-64 Platform:
SUSE LINUX 10.0:
7550e022c5557841a06c6334d1a2632c
b25da775ec60a014febb111179a42e91
SUSE LINUX 9.3:
8ee673f4f3386e6e0a5ea123cad19064
b65ee8de2eae744f40b7d33ae912995c
SUSE LINUX 9.2:
8e4f8794e3f8322b4b5c301d964cfabd
30af3b8e87fe2018ae2b4a1a884887e2
SUSE LINUX 9.1:
dbdf3e6c1d45a0e42f0facfd78edc29c
bcf17a5cd915276de386e8181c87ec99
Sources:
SUSE LINUX 10.0:
6ecfb0963c478d0962fad9146110466c
e8f841c893e062f2e378eb269ba7d128
SUSE LINUX 9.3:
0944add00587f50f20c5f7a38fac5b4f
5d89968ca8f4b1718f0018c8c466ddf9
SUSE LINUX 9.2:
26d12b6a99b2723272a74f402ba4ff58
f097a1113a838a007c586c72bb7e43a2
SUSE LINUX 9.1:
362067f9c39a902c433af5f998b4eecf
b7443b44f2ee6cab65f214e6e983f113
95d18a7cf39acaabb747edfc7b5411cd
517f4afbe1f3d1b3ad554582d4463bb2
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/
______________________________________________________________________________
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:
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.
====================================================================
