If an RSA key with exponent 3 is used it may be possible to forge a If an RSA key with exponent 3 is used it may be possible to forge a PKCS verify the certificate if they are not checking for excess data PKCS verify the certificate if they are not checking for excess data in the RSA exponentiation result of the signature. This problems affects various SSL implementations. This advisory covers th [More...]. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: openssl,mozilla-nss Announcement ID: SUSE-SA:2006:055 Date: Fri, 22 Sep 2006 18:00:00 +0000 Affected Products: Novell Linux Desktop 9 Novell Linux POS 9 Open Enterprise Server SUSE LINUX 10.1 SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SuSE Linux Desktop 1.0 SuSE Linux Enterprise Server 8 SuSE Linux Openexchange Server 4 SUSE LINUX Retail Solution 8 SuSE Linux School Server SuSE Linux Standard Server 8 SUSE SLED 10 SUSE SLES 10 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: RSA signature evasion Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2006-4339, CVE-2006-4340, CVE-2006-4341 Content of This Advisory: 1) Security Vulnerability Resolved: RSA signature evasion 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 If an RSA key with exponent 3 is used it may be possible to forge a PKCS verify the certificate if they are not checking for excess data in the RSA exponentiation result of the signature. This problems affects various SSL implementations. This advisory covers the following implementations: - OpenSSL (CVE-2006-4339) - Mozilla NSS (CVE-2006-4340 and CVE-2006-4341) for SUSE Linux 10.0, 10.1 and SUSE Linux Enterprise 10. Implementations that are affected and still need to be updated: - gnutls in all distributions. - Mozilla NSS before SUSE Linux 10.0 and SUSE Linux Enterprise 10. The official openssl advisory is here: Some details of the actual technical problem can be found here: 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please close and restart running programs using SSL to verify PKCS signatures (web browsers, E-Mail clients, etc.) 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.1: 2ca59cfa949741f970019250db6e7890 5176d16fddcc9085c9c62633df1c1e7a f3c5cb97da8acb6a4c4ef9434cb89e1a 20c03b69fb682e341fbcbd6e0b7fa08d SUSE LINUX 10.0: f1040a75792a24085ffeacaf4fdbbadb f666ce57dcedd14078d2289831658ec2 2a2ec627749b0ebef913522777d6d10a 0889bf02be6b048e62109510b711debf SUSE LINUX 9.3: ef34f676b7c3279c368d044a35761e23 2c0333c5ec9ba7b73c23c35bd8478668 SUSE LINUX 9.2: e059156ac8c786f92915c66101c22cca 163ce037ad79bbf3c53e4182a37c8b1a Power PC Platform: SUSE LINUX 10.1: 6b8a99c4f638adda50eda09925c11983 1e78438027cc3e92e7a65af293142280 a324d27cf6dfa4ceedcf83c1dcffb534 ab05376b3874aa893546a31630b503e8 SUSE LINUX 10.0: 420734304297e8e4f708d83843790ee4 530a0571a379a3b5965c7a16aac74c09 53a2702d6c99c2976730c4eca4f81fa2 ec29d438d00028c4c4937174fd378a49 x86-64 Platform: SUSE LINUX 10.1: 6fa083972df9ae919858f621b1aec930 5ce7f14b2fd30384aa123dd6185f074e 2a4c684d4f59f64d4e25e18ea53f49c5 724ffd5c1123d162f19e3f9a929f2bc7 7016abba594501c51de8f32e4051acec 96413d2dd6658ce9a08d777627e78b0a d2af23fa3cabfb7a4458affcd4f24f89 SUSE LINUX 10.0: f0e48cc8482ffa3d9f557caa8c495189 c5185e5f3ec998948e714231da384fae b872a76bded9ca5fea3a92ea6311a820 4780f468291c749b082c18143319f7e0 a3203768a3736019ef975cfed314ddd3 bc1f3b4a20b4d4a26e22c41700fa7c57 305646efe9293dc744744a9198c9d61b SUSE LINUX 9.3: 0ee8251cc8d18e34683cffb9b836f6d2 01d8ecb0b20265fd547f2f6ce550ef30 e3e7086a44dfd719005b335c90b93dd0 78b2ee77d6a84f3afded42aa048f77b1 SUSE LINUX 9.2: 82bbf9b57187eae584eee9c748471266 8a8ac0b203100e5ac137064760c5e285 153d3ba8a9e7f1179d7495c643a46432 e0e8c2345d6a176e0b79fe1f5ec0b1eb Sources: SUSE LINUX 10.1: 2d64292745510b79081aff63af3ae57c a43b90f75865fbc3596084c35aac3585 SUSE LINUX 10.0: 205b16b750e3fdd4ba3c0b7a12627d6a 7949b6cbcd17092289949e85670e8330 SUSE LINUX 9.3: a3fec9ffa1b2e15fedc51461d603e9c8 SUSE LINUX 9.2: f52a4666f358c6399137c6470c04355d Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: UnitedLinux 1.0 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SuSE Linux Openexchange Server 4 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html Open Enterprise Server http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html Novell Linux POS 9 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html Novell Linux Desktop 9 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SuSE Linux Enterprise Server 8 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SuSE Linux Standard Server 8 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SuSE Linux School Server http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SUSE LINUX Retail Solution 8 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SuSE Linux Desktop 1.0 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SUSE SLES 9 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html SUSE SLES 10 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html http://support.novell.com/techcenter/psdb/a9b0730b9578c91a3685d9913a531d37.html SUSE SLED 10 http://support.novell.com/techcenter/psdb/5ed5dd66328b2d660bce8191dbd9d7de.html http://support.novell.com/techcenter/psdb/a9b0730b9578c91a3685d9913a531d37.html ______________________________________________________________________________ 5) Pending Vulnerabilities, Solutions, and Work-Arounds: See SUSE Security Summary Report. ______________________________________________________________________________ 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 checksumsas 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
Get the latest Linux and open source security news straight to your inbox.