Get the LinuxSecurity news you want faster with RSS
Powered By
SuSE: Weekly Summary 2011:004
Posted by Benjamin D. Thomas
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. List of vulnerabilities in this summary include: exim, krb5, git, dbus-1.
______________________________________________________________________________
SUSE Security Summary Report
Announcement ID: SUSE-SR:2011:004
Date: Tue, 22 Feb 2011 13:00:00 +0000
Cross-References: CVE-2010-2542, CVE-2010-3906, CVE-2010-4022
CVE-2010-4352, CVE-2011-0017, CVE-2011-0281
CVE-2011-0282
Content of this advisory:
1) Solved Security Vulnerabilities:
- exim
- krb5
- git
- dbus-1
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.
- exim
Exim was updated to verify the return value of the setuid/setgid calls
now. (CVE-2011-0017)
Affected Products: openSUSE 11.2, 11.3
- krb5
Multiple KDC DoS vulnerabilities if used with LDAP backends have been
fixed in krb5. CVE-2011-0281 and CVE-2011-0282 have been assigned.
Additionally a DoS vulnerability in kpropd has been fixed in openSUSE.
CVE-2010-4022 has been assigned to this issue.
Affected Products: SLE11-SP1, openSUSE 11.2, 11.3
- git
This update fixes two vulnerabilities:
+ CVE-2010-3906: XSS vulnerability in gitweb; a remote attacker could
craft an URL such that arbitrary content would be inserted to the
generated web page.
+ CVE-2010-2542: Stack overflow vulnerability that can lead to arbitrary
code execution if user runs any git command on a specially crafted git
working copy.
Affected Products: SLE11-SP1, openSUSE 11.2, 11.3
- dbus-1
Local users could crash the D-Bus daemon by sending a specially crafted
message (CVE-2010-4352).
Affected Products: SLE11-SP1
______________________________________________________________________________
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
.
=====================================================================
SUSE's security contact is or .
The public key is listed below.
=====================================================================
______________________________________________________________________________