-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Summary Report Announcement ID: SUSE-SR:2008:016 Date: Fri, 08 Aug 2008 12:13:00 +0000 Cross-References: CVE-2008-3325, CVE-2008-3326, CVE-2008-3078, CVE-2008-3188, CVE-2008-2641, CVE-2008-0668 Content of this advisory: 1) Solved Security Vulnerabilities: - moodle cross-site scripting and cross-site request forgery - Opera 9.51 fixes memory issues - libxcrypt wrong password encryption - acroread unspecified vulnerability - gnumeric integer overflows 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. - moodle cross-site scripting and cross-site request forgery problems An incorrect input validation in moodle could be exploited by remote attackers to inject arbitrary script code or to forge HTTP requests (CVE-2008-3325, CVE-2008-3326). moodle is contained in and was fixed for openSUSE 10.2, 10.3 and 11.0. - Opera 9.51 fixes memory issues Opera did not properly manage memory within functions supporting the CANVAS element. This allowed attackers to read unintitialized memory contents using malicious JavaScript code (CVE-2008-3078). Opera is contained in and was fixed for openSUSE 10.2, 10.3 and 11.0 - libxcrypt wrong password encryption libxcrypt did not encrypt passwords with MD5 when it was selected in its configuration file, instead it always used DES as password encryption algorithm (CVE-2008-3188). Only libxcrypt in openSUSE 11 was affected by the issue and fixed. - acroread unspecified vulnerability An unspecified vulnerability in acroread allowed remote attackers to cause a denial-of-service or possibly execute arbitrary code via unknown vectors. (CVE-2008-2641). acroread was fixed for openSUSE 10.2 and 10.3 - gnumeric integer overflows Due to integer signedness errors it was possible for attackers to execute arbitrary code by the use of specially crafted XLS files (CVE-2008-0668). gnumeric was fixed for openSUSE 10.2 and 10.3 ______________________________________________________________________________ 2) Pending Vulnerabilities, Solutions, and Work-Arounds none listed here ______________________________________________________________________________ 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 --verifyreplacing 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. ====================================================================