June 2001 - openSUSE Security - openSUSE Mailing Lists

Re: [[suse-security] Nessus complains about sendmail]
by Bill Jones 03 Jun '01

03 Jun '01

Not sendmail per se but I believe the exploit exists in the mail command itself. I also do not believe SuSE is vunerable if you have the lastest mail update rpm listed under updates/7.1 But, I've been wrong before ... -Sneex- :] "J. Mell" <mell(a)www.br-wickelsysteme.de> wrote: > Hi list, > Nessus complained that there might be a buffer overflow if the 'MAIL FROM' > command string becomes too long. ____________________________________________________________________ Get free email and a permanent address at http://www.netaddress.com/?N=1

1 0

Nessus complains about sendmail
by J. Mell 03 Jun '01

03 Jun '01

Hi list, today I ran Nessus against our internet server. This server also provides mail services with Sendmail. RPM -q shows Sendmail 8.11.2-4. The system is SuSE 7.1. Nessus complained that there might be a buffer overflow if the 'MAIL FROM' command string becomes too long. As I cannot find anything about this issue in Sendmail's known bugs list and as the running Sendmail did not crash, I wonder if this is some kind of false alarm or a real issue. If it is real, will there be an update? Bye, Jürgen

1 0

SuSE Security Announcement: gpg/GnuPG (SuSE-SA:2001:020)
by Roman Drahtmueller 03 Jun '01

03 Jun '01

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: gpg/GnuPG Announcement-ID: SuSE-SA:2001:020 Date: Sunday, Jun 3rd 2001 14:00 MEST Affected SuSE versions: 6.3, 6.4, 7.0, 7.1, (7.2) Vulnerability Type: local privilege escalation Severity (1-10): 6 SuSE default package: yes Other affected systems: systems shipping the gpg/GnuPG package Content of this advisory: 1) security vulnerability resolved: gpg problem description, discussion, solution and upgrade information 2) pending vulnerabilities, solutions, workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information GnuPG (the SuSE package is named "gpg") is a powerful encryption and signing program with a widespread usership in the free software world. It is designed to be a replacement for PGP and conforms to the OpenPGP standard. A format string vulnerability in versions of GnuPG before 1.0.6 has been found. The error occurs when gpg encounters a filename suffix that is not ".gpg" and prints the filename without the suffix as a default to the terminal. The bug allows an attacker to execute arbitrary code as the user calling gpg. Werner Koch, the author of the GnuPG package, states that when the "--batch" commandline option is used (such as when verifying rpm packages, see Section 3 of this announcement, or when used in MUAs (Mail User Agent)), the error cannot occur since this option supresses the printout of the filename on the terminal. There is no temporary workaround for the problem except for the "--batch" commandline option to gpg. We recommend to update the gpg package on all systems where it is installed. As an additional reason to update the package, it should be noted that gnupg 1.0.5 (packages were available on our ftp server) fixed some security-related problems, where one of them could allow an attacker with access to your key ring to compute the private key in considerably less time. We thank Werner Koch, the author of the GnuPG program, for quickly responding to the problem and fish stiqz, Synnergy Networks, for finding and communicating the problem to Werner Koch and to the security community. Please download the update package from locations described below and check the authenticity of the rpm package file using a method as described in section 3) of this security announcement. Please note that the packages for the 7.1 distribution are located on the ftp.suse.com ftp server, the packages for older distributions are on ftp.suse.de. The upcoming SuSE Linux Distribution 7.2 has been officially announced and will be available for our customers these days. The gpg package in version 1.0.6 did not make it into the 7.2 distribution. The update package will be available in the update directory shortly. Use the command `rpm -Uhv file.rpm' to apply the update. i386 Intel Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/i386/update/7.1/sec1/gpg-1.0.6-0.i386.rpm 39153126feeddf43a939c89a9b1a33fd source rpm: ftp://ftp.suse.com/pub/suse/i386/update/7.1/zq1/gpg-1.0.6-0.src.rpm 318ebedd094da2063ecaf209a9a686be SuSE-7.0 ftp://ftp.suse.de/pub/suse/i386/update/7.0/sec1/gpg-1.0.6-0.i386.rpm b78951d79a8c9593a9baf14963c2eb61 source rpm: ftp://ftp.suse.de/pub/suse/i386/update/7.0/zq1/gpg-1.0.6-0.src.rpm ea2067aacf9fb45d2a94eba066fdc18b SuSE-6.4 ftp://ftp.suse.de/pub/suse/i386/update/6.4/sec1/gpg-1.0.6-1.i386.rpm 6050bffa597965475a4caf0a5c265c23 source rpm: ftp://ftp.suse.de/pub/suse/i386/update/6.4/zq1/gpg-1.0.6-1.src.rpm 320eff2cc72cad2bce555993fbc7cb61 SuSE-6.3 ftp://ftp.suse.de/pub/suse/i386/update/6.3/sec1/gpg-1.0.6-1.i386.rpm 6050bffa597965475a4caf0a5c265c23 source rpm: ftp://ftp.suse.de/pub/suse/i386/update/6.3/zq1/gpg-1.0.6-1.src.rpm 320eff2cc72cad2bce555993fbc7cb61 Sparc Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/sparc/update/7.1/sec1/gpg-1.0.6-0.sparc.rpm 20d3a3d7d65aee48f281edf0ae2f162c source rpm: ftp://ftp.suse.com/pub/suse/sparc/update/7.1/zq1/gpg-1.0.6-0.src.rpm d827d8e68a306c2d7890a5c113d934d3 SuSE-7.0 ftp://ftp.suse.de/pub/suse/sparc/update/7.0/sec1/gpg-1.0.6-0.sparc.rpm fca18e28c3442b16d7aaf614a5bda269 source rpm: ftp://ftp.suse.de/pub/suse/sparc/update/7.0/zq1/gpg-1.0.6-0.src.rpm 797e4f8410e4e4ba159bfc0e3eb7c06c PPC Power PC Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/ppc/update/7.1/sec1/gpg-1.0.6-0.ppc.rpm 9c4c27fd13e9d27ac712bb37cdbe1972 source rpm: ftp://ftp.suse.com/pub/suse/ppc/update/7.1/zq1/gpg-1.0.6-0.src.rpm f262178a3b3d92c6382a303c3aba728e SuSE-7.0 ftp://ftp.suse.de/pub/suse/ppc/update/7.0/sec1/gpg-1.0.6-0.ppc.rpm 378dea2eb7b63ca376330f10757c042e source rpm: ftp://ftp.suse.de/pub/suse/ppc/update/7.0/zq1/gpg-1.0.6-0.src.rpm a1815320cc4537bd18f4c361880c9f44 SuSE-6.4 ftp://ftp.suse.de/pub/suse/ppc/update/6.4/sec1/gpg-1.0.5-3.ppc.rpm d76adf2f7ab76454b05202df580a0235 source rpm: ftp://ftp.suse.de/pub/suse/ppc/update/6.4/zq1/gpg-1.0.5-3.src.rpm bc18a284bfee16e96a2ff7f6749b4cd1 AXP Alpha Platform: SuSE-7.1 ftp://ftp.suse.com/pub/suse/axp/update/7.1/sec1/gpg-1.0.6-0.alpha.rpm 68f791f8d03e3afbad5ee12b529ecc3c source rpm: ftp://ftp.suse.com/pub/suse/axp/update/7.1/zq1/gpg-1.0.6-0.src.rpm 41a50ddce1b16fd91627ac6b155426f6 SuSE-7.0 ftp://ftp.suse.de/pub/suse/axp/update/7.0/sec1/gpg-1.0.6-0.alpha.rpm 696989a2d730b1dbf3891f6b14c42be3 source rpm: ftp://ftp.suse.de/pub/suse/axp/update/7.0/zq1/gpg-1.0.6-0.src.rpm c76556d46b5de45349c146cb9b65b526 SuSE-6.4 ftp://ftp.suse.de/pub/suse/axp/update/6.4/sec1/gpg-1.0.6-1.alpha.rpm e56719ef69aee3a6758f43317cd205cb source rpm: ftp://ftp.suse.de/pub/suse/axp/update/6.4/zq1/gpg-1.0.6-1.src.rpm 6e54ae31543db2c70a3b47f4916e7964 SuSE-6.3 ftp://ftp.suse.de/pub/suse/axp/update/6.3/sec1/gpg-1.0.6-2.alpha.rpm 55cb31d055cfaa7e96908391b075550e source rpm: ftp://ftp.suse.de/pub/suse/axp/update/6.3/zq1/gpg-1.0.6-2.src.rpm e19e2ae8c07e813ff00e65a618046974 ______________________________________________________________________________ 2) Pending vulnerabilities in SuSE Distributions and Workarounds: - qpopper SuSE Linux distributions after SuSE-7.1 contain the qpopper in version 4.x.y. According to the Changelogs of Qpopper 4.0.3 (See ftp://ftp.qualcomm.com/eudora/servers/unix/popper/), the versions of qpopper before version 4.0.3 contain a buffer overflow. We are currently investigating if this bug is exploitable and which versions of qpopper are affected. We will provide update packages as soon as possible if necessary. Please see our upcoming security announcements (Section 3 of this announcement)! - netscape Netscape before Version 4.77 contains a bug that allows a remote attacker to store JavaScript code in the comment field of GIF files that are contained in a viewed page. This code can be executed. Update packages for the SuSE Linux distributions 6.3, 6.4, 7.0 and 7.1 can be found on our ftp server at ftp://ftp.suse.com/pub/suse/i386/update/7.1/xap1/netscape-4.77-21.i386.rpm 1e2de825b3386d80a3731760b9e7f323 ftp://ftp.suse.com/pub/suse/i386/update/7.0/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.4/xap1/netscape-4.77-21.i386.rpm ftp://ftp.suse.com/pub/suse/i386/update/6.3/xap1/netscape-4.77-21.i386.rpm 13f303944c9ac0863591b03c4eb75501 The packages are gpg-signed. See the section above about downloading and verifying rpm packages. The complexity of the netscape browser suggests by nature that more security related problems will be found, we will not issue a dedicated security announcement for the netscape package any more. Security- inclined users may please see the future security announcements in section 2) for information about security related problems with the netscape package. - pine Most of the supported distributions have pine update packages in the update area of the ftp server that update the pine package to version 4.33. Many vulnerabilities have been found in versions before 4.33, and it is recommended to perform the upgrade. Please note that not all packages have been built yet. See the update directory for your distribution (like i386/update/7.0/n1) for pine-4.33 packages. - dqs dex(a)raza-mexicana.org has found an exploitable buffer overflow bug in the dsh program from the dqs package on SuSE Linux distributions. To workaround the problem, do "chmod -s /usr/bin/dsh" and change the files /etc/permissions* to reflect the change. If you do not need the dqs package, then deinstall it (rpm -e dqs). We are working on update packages that fix the problem. - samba Insecure temporary file handling is the cause for a new samba version 2.0.9 that can be found as rpm packages in the n1/ directory of your distribution. It is recommended to install the update package if your users have local shell access to your samba server (this bug is not remotely exploitable). We are currently investigating some oddity in the behaviour of the samba package and will send a security announcement as soon as we have clarified the problems. The problems were present in earlier releases/versions of the samba package as well. By consequence, the installation of the update package is of low risk for the functionality of your system. ______________________________________________________________________________ 3) standard appendix: authenticity verification, additional information - Package authenticity verification: SuSE update packages are available on many mirror ftp servers all over the world. While this service is being considered valuable and important to the free and open source software community, many users wish to be sure about the origin of the package and its content before installing the package. 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) md5sums as provided in the (cryptographically signed) announcement. 2) using the internal gpg signatures of the rpm package. 1) execute the command md5sum <name-of-the-file.rpm> 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 announcement. Since the announcement containing the checksums is cryptographically signed (usually using the key security(a)suse.de), the checksums show proof of the authenticity of the package. We disrecommend to subscribe to security lists which cause the email message containing the announcement to be modified so that the signature does not match after transport through the mailing list software. Downsides: You must be able to verify the authenticity of the announcement in the first place. If RPM packages are being rebuilt and a new version of a package is published on the ftp server, all md5 sums for the files are useless. 2) rpm package signatures provide an easy way to verify the authenticity of an rpm package. Use the command rpm --checksig <file.rpm> to verify the signature of the package, where <file.rpm> is the filename of the rpm package that you have downloaded. Of course, package authenticity verification can only target an uninstalled rpm package file. Prerequisites: a) gpg is installed b) The package is signed using a certain key. The public part of this key must be installed by the gpg program in the directory ~/.GnuPG/ under the user's home directory who performs the signature verification (usually root). You can import the key that is used by SuSE in rpm packages for SuSE Linux by saving this announcement to a file ("announcement.txt") and running the command (do "su -" to be root): gpg --batch; gpg < announcement.txt | gpg --import SuSE Linux distributions version 7.1 and thereafter install the key "build(a)suse.de" upon installation or upgrade, provided that the package gpg is installed. The file containing the public key is placed at the toplevel directory of the first CD (pubring.gpg) and at ftp://ftp.suse.com/pub/suse/pubring.gpg-build.suse.de . - SuSE runs two security mailing lists to which any interested party may subscribe: suse-security(a)suse.com - general/linux/SuSE security discussion. All SuSE security announcements are sent to this list. To subscribe, send an email to <suse-security-subscribe(a)suse.com>. suse-security-announce(a)suse.com - SuSE's announce-only mailing list. Only SuSE's security annoucements are sent to this list. To subscribe, send an email to <suse-security-announce-subscribe(a)suse.com>. For general information or the frequently asked questions (faq) send mail to: <suse-security-info(a)suse.com> or <suse-security-faq(a)suse.com> respectively. =================================================== SuSE's security contact is <security(a)suse.com>. The <security(a)suse.com> public key is listed below. =================================================== Regards, Roman Drahtmueller <draht(a)suse.de>. - - | Roman Drahtmüller <draht(a)suse.de> // "The best way to pay for a | SuSE GmbH - Security Phone: // lovely moment is to enjoy it." | Nürnberg, Germany +49-911-740530 // - Richard Bach | - - ______________________________________________________________________________ The information in this advisory may be distributed or reproduced, provided that the advisory is not modified in any way. SuSE GmbH makes no warranties of any kind whatsoever with respect to the information contained in this security advisory. Type Bits/KeyID Date User ID pub 2048R/3D25D3D9 1999-03-06 SuSE Security Team <security(a)suse.de> pub 1024D/9C800ACA 2000-10-19 SuSE Package Signing Key <build(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.GnuPG.org mQENAzbhLQQAAAEIAKAkXHe0lWRBXLpn38hMHy03F0I4Sszmoc8aaKJrhfhyMlOA BqvklPLE2f9UrI4Xc860gH79ZREwAgPt0pi6+SleNFLNcNFAuuHMLQOOsaMFatbz JR9i4m/lf6q929YROu5zB48rBAlcfTm+IBbijaEdnqpwGib45wE/Cfy6FAttBHQh 1Kp+r/jPbf1mYAvljUfHKuvbg8t2EIQz/5yGp+n5trn9pElfQO2cRBq8LFpf1l+U P7EKjFmlOq+Gs/fF98/dP3DfniSd78LQPq5vp8RL8nr/o2i7jkAQ33m4f1wOBWd+ cZovrKXYlXiR+Bf7m2hpZo+/sAzhd7LmAD0l09kABRG0JVN1U0UgU2VjdXJpdHkg VGVhbSA8c2VjdXJpdHlAc3VzZS5kZT6JARUDBRA24S1H5Fiyh7HKPEUBAVcOB/9b yHYji1/+4Xc2GhvXK0FSJN0MGgeXgW47yxDL7gmR4mNgjlIOUHZj0PEpVjWepOJ7 tQS3L9oP6cpj1Fj/XxuLbkp5VCQ61hpt54coQAvYrnT9rtWEGN+xmwejT1WmYmDJ xG+EGBXKr+XP69oIUl1E2JO3rXeklulgjqRKos4cdXKgyjWZ7CP9V9daRXDtje63 Om8gwSdU/nCvhdRIWp/Vwbf7Ia8iZr9OJ5YuQl0DBG4qmGDDrvImgPAFkYFzwlqo choXFQ9y0YVCV41DnR+GYhwl2qBd81T8aXhihEGPIgaw3g8gd8B5o6mPVgl+nJqI BkEYGBusiag2pS6qwznZiQEVAwUQNuEtBHey5gA9JdPZAQFtOAf+KVh939b0J94u v/kpg4xs1LthlhquhbHcKNoVTNspugiC3qMPyvSX4XcBr2PC0cVkS4Z9PY9iCfT+ x9WM96g39dAF+le2CCx7XISk9XXJ4ApEy5g4AuK7NYgAJd39PPbERgWnxjxir9g0 Ix30dS30bW39D+3NPU5Ho9TD/B7UDFvYT5AWHl3MGwo3a1RhTs6sfgL7yQ3U+mvq MkTExZb5mfN1FeaYKMopoI4VpzNVeGxQWIz67VjJHVyUlF20ekOz4kWVgsxkc8G2 saqZd6yv2EwqYTi8BDAduweP33KrQc4KDDommQNDOXxaKOeCoESIdM4p7Esdjq1o L0oixF12CpkBogQ57vSBEQQAk/GN+ftr7+DBlSoixDDpfRnUk+jApGEt8hCnrnjV nPs/9Cr33+CXLQbILOO7Y5oiPbJdHh45t4E0fKyLVzDerCRFB1swz/mNDxT26DLy sdBV5fwNHTPhxa67goAZVrehQPqJEckkIpYriOaYcKpF3n5fQIZMEfMaHEElQhcX ML8AoJVXDkJYh7vI8EUB8ZURNLZMEECNA/sH0MCnb4Q6ZcRyeZ3+1PHP8hP73b6T epRdLZhaylwVF/iu7uIn62ZUL4//NTOCDY7V63qg4iba/fUbOsWtEnGaiE7mQuAl sSWvRspwRA9/g9rdVf3/JdLJrLmKBTheyG+PSJE3W7cAE4ZWafGxIRCwXhmj3TQn Jn2euqylHRubEQP/aL53NZK0kBdvrKgff6O8Of6tqoss8Dkk55I7QVFSp+My1Dn+ mngQKFejTAgtyo/WmR3wPjQ9HoT2lRiYI2lTRYT4uMdHuwVC3b4DqAKmoy375FER wHkrMVyKBJslv8QtbAWw5A1CAUseaHo+91wmYJ4/4p6YUahqbG/tZyhbxfq0KFN1 U0UgUGFja2FnZSBTaWduaW5nIEtleSA8YnVpbGRAc3VzZS5kZT6IXAQTEQIAHAUC Oe70gQUJA8JnAAQLCgMEAxUDAgMWAgECF4AACgkQqE7a6JyACspfLACffAYA+NM8 NBhyRyH+nTX58CNjwLIAoIx9fj52BJe0xY7WbKoXs1+72b2AiEYEEBECAAYFAjpw XlIACgkQnkDjEAAKq6TczgCgi+ddhWb7+FWcfeE6WwPZccqAHowAnjjtRyGwHLQH r5OTFAYTXi2Wv6jNiQEVAwUQOnBgb3ey5gA9JdPZAQE1pwf/QJ+b34lFBNVUJ7fk /xGJJREt7V12iSafaRzGuH8xWvIz1bb+VARxnnt16FDQ1cDNjoEhCEmcW83Vxp6i JXE9PE8wVA/Yue/bon5JS7J69+UiQ2eq2pudfwljp52lYVM53jgPYEz0q/v3091n lZ8CYkAkN9JDS1lV1gEzJ7J0+POngDpU+lDQT2EC6VKaxeWK8pNt6UFDwICRDQxK nlOoiDvTrdWT7QdJZ4sPv8Qotdw9+tKNbWQ2DqdIRxyTdw9xDfAtcj6mXeQr7852 Lwem1gSKVnEYHZ9g1FTJqVOutY8KhpUc9RfOCRv8XuIxrs4KSbfSF0s8qIRCQelx ufg9AbkCDQQ57vSSEAgAhJHQTejMX+Vr6g1pHDEcusJ63fQ2CfFFE5iE9okH9O7U VCiSfb9CV38dmeHdPCEEjDUWquFYEnvj3WICMtH249t1Ymuf4Du3yRKQ9oXdn/qT Jzlrx9qzjiG3mH7ocwHOgUIwCrZoEdBEVE2n0zPVm+hddwjWWTWXw6pxQz+i9dsN 89xexRV5M9O0bNwCLaNWX2GXeLAkqTK/9EuZy6x2yLxi6du9YYUAXkZpqBhCjtiU XpRoFCdglMznbcAyCk9C2wqb2j/D1Z2BeSBaGCSFkR6pRLebnE17LWcu72Iy+r0z +JecbPiyDpDZj4apn7IC81aNFGi7fNITsHODbwwjiwADBgf/YPvVdzkc8OC7ztac EWCanwylKvxCdKzTDA+DfES6WUYShyiVJvZzRy25LJ5WcK20kzOS6Qv1OrIXiz/p dGy1aKtJZrAnFEsofpmOj8VoqyyFgp/yAGQBp12+mXek7SCZRhuqalDfEMRiWEJ6 J5dLkyShyRDWyPbFh0HXE7QTHN+IKKxxQqNQXL6Z3NSxS61p+5n6BseiDUI39xxk KTFwFrkgUIc5Gs2Or2lhaWvGwSfoCmwbsklszZt6xbU+R0SjFqTvjPWx6eHfqbmN C9WMDdTjGrXDDKXFp2aYlokfN6It9vsbVlGNlOwHt/JjGoPMxW6Xqj0FLA7/Vewg CdXW64hMBBgRAgAMBQI57vSSBQkDwmcAAAoJEKhO2uicgArKSyIAmwUHf/vtKQfc mVg4asR7U6XQl0bAAJ4pO22B5U8UH6IYl2LBCXFqw5+5fA== =rVRn - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOxosAHey5gA9JdPZAQHsygf/ZJ/QnjN5LzpQqYqIU4n5Hd8EqWJN1S83 i4tr+kMJxNqL3E1pXjFOpAxzpqcib5gK8bBsCnlVnjZtUro1eZwhvtZyJZTlBVe/ OO/Vp39Y4LTDXQfTmfl5nqjyVFObcBWI6rYvKxpJgl3mmcsH4HGr0UQXFgg3AnVI +J3TVk2j5pcn7br7XzFFyXzcTc//3PZlKWCNZkajD8JHW1uEuN3OIvojaJhFIvRw bWMtFoX9R7UDByekGFnhO4F7wT36QGvGixnYM9V9/PcrAMprRUQfeey+V3gQrPFZ peUzqm3oT/uWVEldyLyyLbUur3GeIRJweLFYs6OvWYj7BAEXpdsv5w== =doZ/ -----END PGP SIGNATURE-----

1 0

Re: [suse-security] Turning off PC Anywhere
by Sundar ＠local 03 Jun '01

03 Jun '01

When I did 'fuser 5632/udp', I did not get anything back on the console. Should I be explicitly turning off the port? If yes, how do I do it. Thanks, sundar ----- Original Message ----- From: "Anders Johansson" <andjoh(a)cicada.linux-site.net> To: "Sundar @local" <sundar(a)esaravana.com> Sent: Saturday, June 02, 2001 6:00 PM Subject: Re: [suse-security] Turning off PC Anywhere > PC Anywhere is a windows program. nessus is reporting it as such, simply > because the port 5632 is listed in /etc/services as belonging to PC Anywhere, > but ports above 1024 can be opened by any process. try running fuser 5632/udp > on the web server to find the id of the process owning the port. > > Regards > Anders > > On Sunday 03 June 2001 02:54, sundar(a)esaravana.com wrote: > > I ran nessus against my web server running (SuSE 7.1-kernel 2.4), it came > > out with a scan that I am running PC Anywhere in port 5632/udp. I want to > > get > > rid of it. How do I do it and from which package did I get this. > > > > Cheers!, > > Sundar > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-security-help(a)suse.com >

2 1

Turning off PC Anywhere
by Sundar ＠local 03 Jun '01

03 Jun '01

I ran nessus against my web server running (SuSE 7.1-kernel 2.4), it came out with a scan that I am running PC Anywhere in port 5632/udp. I want to get rid of it. How do I do it and from which package did I get this. Cheers!, Sundar

1 0

Secmod/secumod? Where can I find it for SuSE 7.1
by A_Johnson-SuseML-e 02 Jun '01

02 Jun '01

Hello again :) I am still searching for secumod or secmod for my 7.1 pro version. As for those whom have been asking me about insmod..well I know that you are right, it is old and I man using the new version included with 7.1 Also where can I find any FAQ on testing my SuSE servers security vulnerabilities and the such? Aaron L. Johnson

2 1

searching for good WINDOWS security list
by A_Johnson-SuseML-e 02 Jun '01

02 Jun '01

I know I may get flamed here but I do use windows as much as I wish not to....so I am searching for a LIST about windows security. I think I may have a Trojan bot on my machine...akkk, they are like harpies (not herpies but harpies the little baby monsters), and Windows seems to be very susceptible to any germ out there..... PS I know I can set up my linux box to sniff at my windows box... how would I do a thing like that. I was hoping to have a direct link from the WIN to the LINUX for the task...what do I use on the linux box? nmap? I read about that someplace...any other tools? Thaanks... This is why I think I have a bot/Trojan, the first 2 lines, tcp port 1080 and 5000 and 139... they are up even when I have no IP assigned to my NIC, they are always there... and I have no idea is what is going on at those ports. I have a fire wall, Zonealarm and a linksys 4 port router that supports NAT...okay okay I am new to this stuff ....lol...but it's fun in some sick and twisted way that I can not figure out. So FLAME ON he he but with a side of help would be greatly appreciated. :) Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:1080 0.0.0.0:0 LISTENING TCP 0.0.0.0:5000 0.0.0.0:0 LISTENING TCP 24.183.224.125:139 0.0.0.0:0 LISTENING UDP 24.183.224.125:1900 *:* UDP 24.183.224.125:137 *:* UDP 24.183.224.125:138 *:* UDP 127.0.0.1:1026 *:* UDP 127.0.0.1:1041 *:* UDP 127.0.0.1:1095 *:* Aaron L Johnson

4 3

RE: [suse-security] Strange apache log entry
by Peer Stefan 02 Jun '01

02 Jun '01

Ok, Microsoft Frontpages has several security flaws, but that does not automatically mean that every request for _vti_<whatever> is done by a hacker or a script-kiddy. Have a look at the browser the client is using, if it's "MSFrontPage/X.Y" then please don't worry. But do worry if it's the only request for a link containing _vti* or if there is only one client (if it's not a proxy) requesting this url. Watch your system, but don't worry to much. regards, Stefan Peer -----Ursprüngliche Nachricht----- Von: Soeren Todt [mailto:sworn@gmx.net] Gesendet: Donnerstag, 31. Mai 2001 15:30 An: suse-security(a)suse.com; Thorsten Marquardt Betreff: Re: [suse-security] Strange apache log entry Hi, ----- Original Message ----- From: "Thorsten Marquardt" <thom(a)kaupp.chemie.uni-oldenburg.de> To: <suse-security(a)suse.com> Sent: Thursday, May 31, 2001 1:45 PM Subject: [suse-security] Strange apache log entry > my logfiles reports 404 requests to /_vti_bin/shtml.exe/_vti_rpc and similar. > > Is this a kind of hacker attack? Maybe you find it out by yourself using a search engine: http://www.google.de/search?q=_vti_bin%2Fshtml.exe%2F_vti_rpc++crack&hl=de&s afe=off then you get results like this: http://www.insecure.org/sploits/Microsoft.frontpage.insecurities.html Ciao Sören --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com For additional commands, e-mail: suse-security-help(a)suse.com

4 3

Firewall2-custom.rc.config
by Shonne Beavers 02 Jun '01

02 Jun '01

My Firewall2-custom.rc.config will not load. What am I doing wrong? Any Dumb User Friendly Answers are appreciated ###Firewall2-custom.rc.config### # Copyright (c) 1999,2000 SuSE GmbH Nuernberg, Germany. All rights reserved. # # Authors: Marc Heuse <marc(a)suse.de>, # Volker Kuhlmann <kuhlmav(a)elec.canterbury.ac.nz> # # /etc/rc.config.d/firewall-custom.rc.config # # ------------------------------------------------------------------------ # # This is file is for SuSEfirewall >= v4.0 and is an example for using # the hooks which are supplied since v4.0 to load customized ipchains rules. # # THERE IS NO HELP FOR USING HOOKS EXCEPT THIS FILE ! SO READ CAREFULLY ! # IT IS USEFUL TO CROSS-READ /sbin/SuSEfirewall TO SEE HOW HOOKS WORK ! # # ------------------------------------------------------------------------ fw_custom_before_antispoofing() { # these rules will be loaded before any anti spoofing rules will be # loaded. Effectively the only filter lists already effective are # 1) allow any traffic via the loopback interface, 2) allow DHCP stuff, # 3) allow SAMBA stuff [2 and 3 only if FW_SERVICE_... are set to "yes"] # You can use this hook to prevent logging of uninteresting broadcast # packets or to allow certain packet through the anti-spoofing mechanism. #example: allow incoming multicast packets for any routing protocol #ipchains -I input -j ACCEPT -d 224.0.0.0/24 true } fw_custom_before_port_handling() { # could also be named "after_antispoofing()" # these rules will be loaded after the anti-spoofing and icmp handling # but before any IP protocol or TCP/UDP port allow/protection rules # will be set. # You can use this hook to allow/deny certain IP protocols or TCP/UDP # ports before the SuSEfirewall generated rules are hit. #example: always filter backorifice/netbus trojan connect requests and log them. iptables -A INPUT -j DROP -p tcp --destination-port 31337 iptables -A INPUT -j DROP -p udp --destination-port 31337 iptables -A INPUT -j DROP -p tcp --destination-port 12345:12346 iptables -A INPUT -j DROP -p udp --destination-port 12345:12346 # Syn-flood protection: iptables -N syn-flood iptables -A INPUT -i eth0 -p tcp --syn -j syn-flood iptables -A syn-flood -m limit --limit 1/s --limit-burst 4 -j RETURN iptables -A syn-flood -j DROP ## Make sure NEW tcp connections are SYN packets iptables -A INPUT -i eth0 -p tcp ! --syn -m state --state NEW -j DROP ## Fragments iptables -A INPUT -i eth0 -f -j LOG --log-prefix "IPTABLES FRAGMENTS: " iptables -A INPUT -i eth0 -f -j DROP ## What if I get spoofed # Refuse packets claiming to be from a Class A private network. iptables -A INPUT -i eth0 -s 10.0.0.0/8 -j DROP # Refuse packets claiming to be from a Class B private network. iptables -A INPUT -i eth0 -s 172.16.0.0/12 -j DROP # Refuse packets claiming to be from a Class C private network. iptables -A INPUT -i eth0 -s 192.168.0.0/16 -j DROP # Refuse Class D multicast addresses. Multicast is illegal as a source address. iptables -A INPUT -i eth0 -s 224.0.0.0/4 -j DROP # Refuse Class E reserved IP addresses. iptables -A INPUT -i eth0 -s 240.0.0.0/5 -j DROP # Furtive port scanner: iptables -A FORWARD -p tcp --tcp-flags SYN,ACK,FIN,RST RST -m limit --limit 1/s -j ACCEPT # Ping of death: iptables -A FORWARD -p icmp --icmp-type echo-request -m limit --limit 1/s -j ACCEPT # Refuse those that think that they are local, me as well iptables -A INPUT -i eth0 -d 127.0.0.1/8 -j DROP # All you can eat Local traffic iptables -A INPUT -i lo -j ACCEPT iptables -A OUTPUT -o lo -j ACCEPT ## AUTH server # Reject ident probes witha tcp reset iptables -A INPUT -i eth0 -p tcp --dport 113 -j REJECT --reject-with tcp-reset true } fw_custom_before_masq() { # could also be named "after_port_handling()" # these rules will be loaded after the IP protocol and TCP/UDP port # handling, but before any IP forwarding (routing), masquerading # will be done. # NOTE: reverse masquerading is before directly after # fw_custom_before_port_handling !!!! # You can use this hook to ... hmmm ... I'm sure you'll find a use for # this ... true } fw_custom_before_denyall() { # could also be named "after_forwardmasq()" # these are the rules to be loaded after IP forwarding and masquerading # but before the logging and deny all section is set by SuSEfirewall. # You can use this hook to prevent the logging of annoying packets. #example: prevent logging of talk requests from anywhere iptables -A INPUT -j DROP -p udp --destination-port 517:518 true }

1 0

Firewall setup
by Oyku Gencay 01 Jun '01

01 Jun '01

Hi, Has anybody used Linux in a such setup? Firewall box 3 ethernets. eth0: internet (Real IP) eth1: Local (192.168.1.0/24) eth2: DMZ (10.0.0.0/24) My problem is rather conceptual. What I'm trying to do is network address translation (NAT) but it's a wide topic and full of misconceptions and incompatibilities between documents. I specifically would like to translate 1 real IP to 1 unreal IP and 1-1 only. For instance; www.xxx.com is 195.195.195.10 (supposed to be a real IP) in the DNS. www.xxx.com runs on the virtual server 10.0.0.10 so the port 80 request to IP 195.195.195.10 should be routed to eth2 and translated as 10.0.0.10 back and forth. What tools do I need for such a setup in a 2.4 kernel ? Thanks in advance

2 2