SUSE Security Summary Report: SUSE-SR:2010:022
Posted on: 11/30/2010 01:57 PM

SUSE published a new Security Summary Report

SUSE Security Summary Report

Announcement ID: SUSE-SR:2010:022
Date: Tue, 30 Nov 2010 12:00:00 +0000
Cross-References: CVE-2010-1172, CVE-2010-2948, CVE-2010-2949
CVE-2010-3702, CVE-2010-3704, CVE-2010-3864

Content of this advisory:
1) Solved Security Vulnerabilities:
- gdm
- openssl/libopenssl-devel
- poppler/libpoppler4/libpoppler-devel
- quagga
2) Pending Vulnerabilities, Solutions, and Work-Arounds:
none
3) Authenticity Verification and Additional Information

______________________________________________________________________________

1) Solved Security Vulnerabilities

To avoid flooding mailing lists with SUSE Security Announcements for minor
issues, SUSE Security releases weekly summary reports for the low profile
vulnerability fixes. The SUSE Security Summary Reports do not list or
download URLs like the SUSE Security Announcements that are released for
more severe vulnerabilities.

Fixed packages for the following incidents are already available on our FTP
server and via the YaST Online Update.

- gdm
This update provides the following fixes:
- 633655: Change the way dbus properties are exported to avoid write
access to read-only properties.
- 627893: Upon relogin gdm displays the Windows domain, but tries to
authenticate locally
- 490621: Windows domain not remembered from previous log-in
- 583060: Optionally allow to configure to prohibit end user to use
"root" id at gdm login
- 506917: Fix window login getting a huge horizontal size
- 627893: Fix that upon relogin gdm displays the Windows domain, but
tries to authenticate locally.
In addition this update was rebuilt against the latest dbus-glib bindings
to avoid that local users can write properties that were exported read-
only via dbus (CVE-2010-1172).
Affected Products: SLE11, SLE11-SP1

- openssl/libopenssl-devel
Multithreaded OpenSSL servers using the TLS server
extension are vulnerable to a buffer overrun attack. CVE-2010-3864
has been assigned to this issue.
Affected Products: SLE11, SLE11-SP1, openSUSE 11.1, 11.2, 11.3

- poppler/libpoppler4/libpoppler-devel
Specially crafted PDF files could crash poppler or potentially even
cause execution of arbitrary code (CVE-2010-3702, CVE-2010-3704)
Affected Products: SLE10-SP3, SLE11, SLE11-SP1, openSUSE 11.1, 11.2, 11.3

- quagga
This update of quagga fixes two security issues:
- CVE-2010-2948: CVSS v2 Base Score: 6.5 (AV:N/AC:L/Au:S/C:P/I:P/A:P)
Stack-based buffer overflow while processing malformed Route-Refresh
messages.
- CVE-2010-2949: CVSS v2 Base Score: 5.0 (AV:N/AC:L/Au:N/C:N/I:N/A:P)
Denial of service while processing malformed BGP update AS path
messages
Affected Products: SLE10-SP3, SLE11, SLE11-SP1, openSUSE 11.1, 11.2, 11.3

______________________________________________________________________________

2) Pending Vulnerabilities, Solutions, and Work-Arounds

none
______________________________________________________________________________

3) 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 containing 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 integrity of a
package needs to be verified to ensure that it has not been tampered with.

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 included at the end of this
announcement.

- 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
.



Printed from Linux Compatible (http://www.linuxcompatible.org/news/story/suse_security_summary_report_suse_sr2010022.html)