Stay Secure with the Latest Linux Advisories

security advisoryremote code executionmoderate severity

SUSE: 2006-008 Moderate: openssh Remote Code Execution Risk

A problem in the handling of scp in openssh could be used to execute A problem in the handling of scp in openssh could be used to execute commands on remote hosts even using a scp-only configuration. commands on remote hosts even using a scp-only configuration. This requires doing a remote-remote scp and a hostile server. (CVE-2006-0225) On SUSE Linux Enterprise Server 9 the xauth pollution prob [More...]. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ______________________________________________________________________________ SUSE Security Announcement Package: openssh Announcement ID: SUSE-SA:2006:008 Date: Tue, 14 Feb 2006 11:00:00 +0000 Affected Products: SUSE LINUX 10.0 SUSE LINUX 9.3 SUSE LINUX 9.2 SUSE LINUX 9.1 SuSE Linux Desktop 1.0 SuSE Linux Enterprise Server 8 SUSE SLES 9 UnitedLinux 1.0 Vulnerability Type: remote code execution Severity (1-10): 7 SUSE Default Package: yes Cross-References: CVE-2006-0225 Content of This Advisory: 1) Security Vulnerability Resolved: scp double expansion 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 A problem in the handling of scp in openssh could be used to execute commands on remote hosts even using a scp-only configuration. This requires doing aremote-remote scp and a hostile server. (CVE-2006-0225) On SUSE Linux Enterprise Server 9 the xauth pollution problem was fixed too. The security fix changes the handling of quoting filenames which might break automated scripts using this functionality. Please check that your automated scp scripts still work after the update. 2) Solution or Work-Around There is no known workaround, please install the update packages. 3) Special Instructions and Notes Please restart the sshd service after the update. 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.0: 3b4e0557d7d0a2b1d23b2c426af95df9 ac11a5ad265e171674485961472baaaf SUSE LINUX 9.3: 2c6d16e14134a1a4f1aaba9ac4aef97f 4cab20c7e83f6de0e440383939e69ec5 SUSE LINUX 9.2: 9b8cf778290ac743fd07445799f79b1f 003115e216c2b36da09ec3679744ba3d SUSE LINUX 9.1: 6e89bdd71e10933bf8e95dc7fad0c289 3d0446f739bcea3715e6945d253b0d53 Power PC Platform: SUSE LINUX 10.0: 3970357da536041d1ae3f7e42655aac7 6a79a95ece5bc7738998adad11205f2f x86-64 Platform: SUSE LINUX 10.0: e9eec927db0859a76851d1b94fa7923d b4a2b9cf969794d1deb1abd07f192786 SUSE LINUX 9.3: 65416ca8578374fa4db63ed9e67f41a3 3fef6bb43541532a654b09dd46201f69 SUSE LINUX 9.2: 3373a79ef05695446f72fdc1a3ec2d44 37ac73c4c9a7723fdcaeb16671b4c6b9 SUSE LINUX 9.1: d04d20e03a63676d5c3349c382318194 ea0deb3eef9970963af2c8c0adce6a7b Sources: SUSE LINUX 10.0: 97ffd38b1144c4797d474c7de1eb6f51 SUSE LINUX 9.3: 1d43324b9d51941bf60e8e0bcbfa25c7 SUSE LINUX 9.2: 647e4b45eba8dd5399c30dcb64db0c91 SUSE LINUX 9.1: cf86431c7c2b1b0b58f6a5f4fff92893 c04ea03236cd9955c5f21f8c15a35416 Our maintenance customers are notified individually. The packages are offered for installation from the maintenance web: https://www.suse.com:443/ ______________________________________________________________________________ 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 updatepackages 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 checksums as 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 This email address is being protected from spambots. You need JavaScript enabled to view it. 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 at the end of this announcement. 2) If you need an alternative means of verification, use the md5sum command to verify the authenticity of the packages. Execute the command md5sum after you downloaded the file from a SUSE FTP server or its mirrors. Then compare the resulting md5sum with the one that is listed in the SUSE security announcement. Because the announcement containing the checksums is cryptographically signed (by This email address is being protected from spambots. You need JavaScript enabled to view it.), the checksums show proof of the authenticity of the package if the signature of the announcement is valid. Note that the md5 sums published in the SUSE Security Announcements are valid for the respective packages only. Newer versions of these packages cannot be verified. - SUSE runs two security mailing lists to which anyinterested party may subscribe: This email address is being protected from spambots. You need JavaScript enabled to view it. - General Linux and SUSE security discussion. All SUSE security announcements are sent to this list. To subscribe, send an e-mail to . This email address is being protected from spambots. You need JavaScript enabled to view it. - SUSE's announce-only mailing list. Only SUSE's security announcements are sent to this list. To subscribe, send an e-mail to . For general information or the frequently asked questions (FAQ), send mail to or . ==================================================================== SUSE's security contact is or . The public key is listed below. ==================================================================== . The recent OpenSSH upgrade rectifies critical code execution flaws affecting several SUSE Linux versions. Implement updates immediately.. OpenSSH Update, Remote Code Execution, SUSE Linux Security, Open Source Risks, Linux Patches. . Severity: Important. LinuxSecurity.com Team

Feb 14, 2006 •Important SuSE