SUSE Security Summary Report: SUSE-SR:2011:001
Posted on: 01/11/2011 01:23 PM

SUSE published their SUSE Security Summary Report

______________________________________________________________________________

SUSE Security Summary Report

Announcement ID: SUSE-SR:2011:001
Date: Tue, 11 Jan 2011 10:00:00 +0000
Cross-References: CVE-2010-1455, CVE-2010-2283, CVE-2010-2284
CVE-2010-2285, CVE-2010-2286, CVE-2010-2287
CVE-2010-2761, CVE-2010-2891, CVE-2010-2992
CVE-2010-2993, CVE-2010-2994, CVE-2010-2995
CVE-2010-3445, CVE-2010-3912, CVE-2010-4180
CVE-2010-4254, CVE-2010-4300, CVE-2010-4301
CVE-2010-4528

Content of this advisory:
1) Solved Security Vulnerabilities:
- finch/pidgin
- libmoon-devel/moonlight-plugin
- libsmi
- openssl
- perl-CGI-Simple
- supportutils
- wireshark
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.

- finch/pidgin
A NULL pointer dereference DoS has been fixed in pidgin.
CVE-2010-4528 has been assigned to this issue.

Affected products: openSUSE 11.2-11.3

- libmoon-devel/moonlight-plugin
Untrusted Moonlight apps could bypass constraints on methods which
potentially allowed attackers to execute arbitrary code (CVE-2010-4254).

Affected products: SLE11-SP1

- libsmi
This update fixes a buffer overflow the smiGetNode() function in libsmi.
It allowed context-dependent attackers to execute arbitrary code via an
Object Identifier.
CVE-2010-2891: CVSS v2 Base Score: 7.5 (HIGH)
(AV:N/AC:L/Au:N/C:P/I:P/A:P): Buffer Errors (CWE-119)

Affected products: openSUSE 11.1-11.3


- openssl
Malicious clients could downgrade a connection to a low strength cipher
suite on session resumption if the server offers such ciphers
(CVE-2010-4180).

Affected products: openSUSE 11.1-11.3, SLE11-SP1

- perl-CGI-Simple
A HTTP header injection attack was fixed in perl-CGI-Simple.
CVE-2010-2761 has been assigned to this issue.

Affected products: openSUSE 11.2-11.3

- supportutils
the supportconfig script did not disguise passwords in the config files
it collected (CVE-2010-3912).

Affected products: SLE11-SP1, SLE10-SP3

- wireshark
Wireshark version 1.4.2 fixes several security issues that allowed
attackers to crash wireshark or potentially even execute arbitrary code

(CVE-2010-1455, CVE-2010-2283, CVE-2010-2284, CVE-2010-2285,
CVE-2010-2286, CVE-2010-2287, CVE-2010-2992, CVE-2010-2993,
CVE-2010-2994, CVE-2010-2995, CVE-2010-3445, CVE-2010-4300,
CVE-2010-4301)

Affected products: openSUSE 11.1


______________________________________________________________________________

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_sr2011001.html)