August 2000 - openSUSE Security - openSUSE Mailing Lists

SuSE Security Announcement: Netscape
by Roman Drahtmueller 31 Aug '00

31 Aug '00

-----BEGIN PGP SIGNED MESSAGE----- ______________________________________________________________________________ SuSE Security Announcement Package: Netscape, Versions 4.x, possibly others Date: Wednesday, August 23rd, 2000 03:30 MEST Affected SuSE versions: All Vulnerability Type: remote file viewing, remote buffer overflow Severity (1-10): 4, 7 SuSE default package: yes Other affected systems: all linux systems using this package Content of this advisory: 1) security vulnerability resolved: Netscape problem description, discussion, solution and upgrade information 2) Correction/apology for perl thread, pending vulnerabilities, temporary workarounds 3) standard appendix (further information) ______________________________________________________________________________ 1) problem description, brief discussion, solution, upgrade information Two security problems exist in the netscape package as shipped with SuSE Linux distributions. a) Improper verification in Netscape's jpeg processing code can lead to a buffer overflow where data read from the network can overwrite memory. As a result, arbitrary code from a remote origin could be executed. The attack is particularly dangerous since it can penetrate firewall setups. Netscape version 4.74 fixes (fixed) this vulnerability. b) Due to an error in the java implementation in Netscape, it is possible for an attacker to view files and directories with the priviledges of the user running Netscape if the user visits a malisciously crafted webpage. This issue is known as "Brown Orifice" and requires the user to have Java enabled in her browser configuration. Again, this attack can penetrate firewall setups. See http://www.brumleve.com/BrownOrifice for details. Problem a) can be circumvented by disabling the automatic image loading in Netscape's configuration. The temporary workaround for problem b) is to disable Java in Netscape's configuration menu (to protect against other vulnerabilities, disable JavaScript, too!). Both countermeasures may widely be found inacceptable. SuSE provides an updated package for the vulnerable software. It is strongly recommended to upgrade to the latest version found on our ftp server as described below. The update package introduces Netscape version 4.75, including the SuSE-specific libraries that fix some of Netscape's "irregular" behaviour. Please note that Netscape-4.75 is not available for the glibc-2.0-based SuSE Distributions SuSE-6.0 and 6.1 because Netscape doesn't provide any files for this glibc version. For these distributions, we provide Netscape Version 4.74 which fixes problem a) only. Alternatively, the package for the libc5-based SuSE-5.3 distribution can be used as well if the package 'shlibs5' is installed. This is recommended, since the 5.3 package may be faster and more reliable. Download the update package as described below and install the package with the command `rpm -Fhv file.rpm'. The md5sum for each file is in the line below. You can verify the integrity of the rpm files using the command `rpm --checksig --nogpg file.rpm', independently from the md5 signatures below. Due to US-American export restrictions for cryptographical software, we are unable to provide update packages on our US ftp server ftp.suse.com. Instead, the packages can be found on ftp.suse.de. For bandwidth reasons, please use our mirrors or our primary mirror ftp.gwdg.de and follow the directory to your distribution. Example: For SuSE-6.4 use the path ftp://ftp.gwdg.de/pub/linux/suse/6.4_update_de/xap1/netscape.rpm. *********************************************************************** Please note that the path to netscape.rpm in the 6.0 and 6.1 update directories point to Netscape version 4.74 which doesn't fix problem b! See section above! *********************************************************************** Further mirrors can be found at http://www.suse.de/de/support/download/ftp/inland.html, but be advised that not all sites mirror the German part of the update directories. md5sums for the i386 Intel Platform (the only one supported): SuSE Versions 6.2, 6.3, 6.4, 7.0: 70289f88b4c9fc1a9867ba7dac985982 netscape-4.75.glibc21.i386.rpm SuSE Version 5.3 (libc5-based, probably faster, can be used on glibc2-based systems if the package shlibs5 is installed) 679aaf67592244a07733bdabdab67729 netscape-4.75.libc5.i386.rpm SuSE Version 6.0 and 6.1, Netscape-4.74 with incomplete fixes: 4bcc31fe37f7c8d226b437c1daa9b944 netscape-4.74.glibc20.i386.rpm ______________________________________________________________________________ 2) Correction/Apology: In my posting to suse-security(a)suse.de and to bugtraq(a)securityfocus.com about the suidperl thread, Subject: "SuSE Security Announcement: suidperl (perl)", dated 10 Aug 2000, I wrote: "A maliciously implemented feature causes the interpreter to spawn the /bin/mail program to"..." This is a bad and embarrassing mistake because of a confusion about the word "maliciously" in this context - it was meant to read "inconsiderate". I apologize to the perl folks for this mistake. Pending vulnerabilities in SuSE Distributions and Workarounds: This section addresses currently known vulnerabilities in Linux/Unix systems that have not been resolved yet as of the release date of this advisory. - ntop ntop is a network statistics visualization utility which offers graphical analysis of network traffic and other statistics with a web browser. By default, ntop listens on port 3000 and requires no or a commonly known authentication password to view the data. ntop is only installed in network server selections and is not activated by default in SuSE Linux installations. The ntop packages shipped with SuSE Linux did not exhibit the unsafe behaviour when a file like /../../etc/passwd is referenced. However, Thomas Biege has reviewed the source of the package and there are still some potential problems with the package that require a major overhaul of the code. Currently, we recommend to disable or even remove the ntop package (`rpm -e ntop') in an environment where security considerations play a role. More information on ntop can be found in ntop's documentation directory /usr/doc/packages/ntop or /usr/share/doc/packages/ntop for SuSE-7.0. - zope SuSE distributions before 7.0 do not contain zope as a package. An updated package for the freshly released SuSE-7.0 is on the way. - xchat A fix for the URL handler vulnerabilty is in progress and will be released within a few days. There is currently no effective and easy workaround other than removing the package by hand (`rpm -e xchat'). More information on xchat can be found in xchat's documentation directory /usr/doc/packages/xchat or /usr/share/doc/packages/xchat for SuSE-7.0. - minicom SuSE's minicom doesn't exhibit the problem with files created belonging to group uucp because /usr/bin/minicom isn't installed sgid uucp by default. Changing this to 2755 root.uucp (manually and in /etc/permissions) doesn't show any defective behaviour either. - xlockmore: After a review of the relevant part of xlock's code we've found that the format string parsing bug posted by bind(a)SUBTERRAIN.NET on bugtraq on August 15th 2000 is not critical wrt security. xlock drops all privs as soon as it could get hold of the user's encrypted password (which is before it crashes). Other encrypted passwords can't be found in xlock's memory. Since xlock on SuSE distributions runs sgid shadow, it can't dump a core file upon segmentation fault (search /usr/src/linux/kernel/sys.c for "dumpable".) and also can't be traced (/usr/src/linux/arch/i386/kernel/ptrace.c). The bug will be fixed in future releases of the SuSE Linux distribution. The following packages are not contained in SuSE distributions. Therefore, they do not impose any security risks on SuSE systems unless an administrator installed (compiled) the vulnerable software by hand. - FlagShip permissions, from Narrow <nss(a)privacyx.com> on bugtraq dated 10 Aug 2000 - VariCAD permissions with RedHat 6.0, from Narrow <nss(a)privacyx.com> on bugtraq dated 10 Aug 2000 - usermode, from Connectiva on bugtraq, dated 2000-08-10 - gopherd 2.x, from Mike Schiffman <michael.schiffman(a)guardent.com> (guardent) on bugtraq, dated 10 Aug 2000, + Chris Sharp <v9(a)FAKEHALO.ORG> on bugtraq dated 20 Aug 2000. - diskcheck perl script, Connectiva sec. adv. on bugtraq dated 2000-08-10 - Statistics Server 5.02x, overflow, from |Zan <izan(a)DEEPZONE.ORG> on bugtraq, dated 10 Aug 2000 - Helix GNOME Updater (helix-update), versions 0.1 through 0.5, from HELIX CODE, INC., on bugtraq, dated 20 Aug 2000 - Darxite overflows, from Guido Bakker <guidob(a)MAINNET.NL> on bugtraq, dated 21 Aug 2000 - Gnome-Lokkit ports left exposed, from Alan Cox <alan(a)LXORGUK.UKUU.ORG.UK> on bugtraq dated 19 Aug 2000 ______________________________________________________________________________ 3) standard appendix: 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>. =============================================== Regards, Roman Drahtmüller. - - -- - - | Roman Drahtmüller <draht(a)suse.de> // "Caution: Cape does | SuSE GmbH - Security Phone: // not enable user to fly." | Nürnberg, Germany +49-911-740530 // (Batman Costume warning label) | - - ______________________________________________________________________________ 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 2048/3D25D3D9 1999/03/06 SuSE Security Team <security(a)suse.de> - -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.3i 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 L0oixF12Cg== =pIeS - -----END PGP PUBLIC KEY BLOCK----- -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv iQEVAwUBOaMtk3ey5gA9JdPZAQECJAf/eWj7H2yFpHj2Rl812BmXD26brkI7wKCR NoxhboH2XcHxxOLK2A1gmFjde5lm9g7iatdytOLYiczz0QqigLgMkqeXGGRxmL6a ODWM+qdHOzIJ+f6G+DsECtYiH+Ez7O1tkuXfFxhW0457dp6o4Vngs2ykF5ITX3Af i0F9KJwb7P7ZNyhQ+q8jwLpts58cCAoyAASVy3vRzGNYFggoj4reXf82Bo+cbYpE +0jd9UpBtkVUACWdf3HaXcVaq7SyVnuNAsXIbSz/5XvH54WJLggmUV0sn+siy/lF gIe/68wtuAJI27LeDcIrskzxFBNs4L5+/QmDqGI1slIM+CtrWbRPBw== =t7fJ -----END PGP SIGNATURE-----

9 11

port 8
by Russell Evans 31 Aug '00

31 Aug '00

I am running the firewall update for SuSE 6.4 with the following settings. FW_DEV_WORLD="eth0" FW_DEV_INT="" FW_DEV_DMZ="" FW_ROUTE="no" FW_MASQUERADE="no" FW_MASQ_NETS="" FW_MASQ_DEV="$FW_DEV_WORLD" FW_PROTECT_FROM_INTERNAL="yes" FW_AUTOPROTECT_GLOBAL_SERVICES="yes" FW_SERVICES_EXTERNAL_TCP="22 53 110 25" FW_SERVICES_EXTERNAL_UDP="514 53" FW_SERVICES_DMZ_TCP="" FW_SERVICES_DMZ_UDP="" FW_SERVICES_INTERNAL_TCP="" FW_SERVICES_INTERNAL_UDP="" FW_TRUSTED_NETS="" FW_SERVICES_TRUSTED_TCP="" FW_SERVICES_TRUSTED_UDP="" FW_ALLOW_INCOMING_HIGHPORTS_TCP="dns" FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" FW_SERVICE_DNS="yes" FW_SERVICE_DHCLIENT="no" FW_SERVICE_DHCPD="no" FW_FORWARD_TCP="" FW_FORWARD_UDP="" FW_REDIRECT_TCP="" FW_REDIRECT_UDP="" FW_LOG_DENY_CRIT="yes" FW_LOG_DENY_ALL="yes" FW_LOG_ACCEPT_CRIT="yes" FW_LOG_ACCEPT_ALL="no" FW_KERNEL_SECURITY="yes" FW_STOP_KEEP_ROUTING_STATE="no" FW_ALLOW_PING_FW="yes" FW_ALLOW_PING_DMZ="no" FW_ALLOW_FW_TRACEROUTE="no" FW_ALLOW_FW_SOURCEQUENCH="yes" FW_MASQ_MODULES="autofw cuseeme ftp irc mfw portfw quake raudio user vdolive" The following was logged. My hostname and IP changed. Aug 27 20:06:14 noname kernel: Packet log: input ACCEPT eth0 PROTO=1 24.8.72.245:8 xxx.yyy.zzz.www:0 L=36 S=0x00 I=56281 F=0x0000 T=118 (#6) Is this a hole in the firewall setup? I do not have the experience to know. Thank you Russell

1 0

bootscreen
by Peter ten Have 30 Aug '00

30 Aug '00

Hello all, However not directly a security (only sniffing) question maybe you've an answer ready. My Linux box is acting as a router and has no monitor attached to it (console) so on reboot I'm not able to follow startup of the services when entering runlevel 2. Is there an easy way to redirect these messages into a file? Thanx, Peter

4 3

Re: [suse-security] Re: Secure By Default - PLEASE!
by dproc＠dol.net 30 Aug '00

30 Aug '00

On Tue, 22 Aug 2000, juergen.braukmann(a)ruhr-west.de wrote: > > that includes telnet etc) and safe: just the safe services (ssh et > > all). That would mean including 3 versions of inetd.conf and rc.config, > > each with a short description of the differences/potential problems. That > > good in theory but... Say, you select "secure inetd" and you select > "Apache". secure inetd will close port 80. Apache needs port 80. Hmmm. > Either Apache would auto select "less secure inetd.conf" or apache / > httpd / THE HELP SYSTEM would not work. Lot's of fun for the newbe that > sais "I want it secure, but why does help not work" (Sorry for the late entry to this thread - I am catching up on a full mailbox) I think your example is wrong at least for 6.3 I activated the help system using rc.config. httpd ports are disabled in inetd.conf. But 6.3 and 5.3 YaST1 can run httpd as a daemon in runlevel 2 - so port 80 remains open all the time. Running httpd this normal way means it is not protected by inetd.conf or hosts.deny. Try it out. I think there is more than one rc.config option so you are correct, it would be easy to confuse a newbie and make help fail. BTW - I know I can protect my help system daemon with a firewall packet filter and with inetd/tcpd. I only want it to work for localhost - everyone else should see dropped connections ideally. But is there an application level way to protect it also - in case my firewall fails? dproc

2 1

Re: [suse-security] bootscreen
by Kalle Kivimaa 30 Aug '00

30 Aug '00

Markus Gaugusch <markus(a)gaugusch.dhs.org> contributed: > i'd also like to redirect output of initscripts to a file for all my > servers i can't reach because they are far away :) The solution below is untested as I personally don't require the functionality and have no machine to test it on right now :/ /etc/rc.d/rc: Add the following line right above "exec 0<> $CONSOLE 1>&0 2>&0": export CONSOLE=/var/log/lastinit

1 0

Re: [suse-security] port 8
by semat＠wawa.eahd.or.ug 30 Aug '00

30 Aug '00

> Aug 27 20:06:14 noname kernel: Packet log: input ACCEPT eth0 PROTO=1 > 24.8.72.245:8 xxx.yyy.zzz.www:0 L=36 S=0x00 I=56281 F=0x0000 T=118 > (#6) > > > Is this a hole in the firewall setup? I do not have the experience to > know. > > Thank you > Russell Most likely this was just a normal ping. Alook at /etc/protocols will show you that proto=1 is icmp.

1 0

Re: [suse-security] port 8
by Bastian Friedrich 30 Aug '00

30 Aug '00

Hi! Russell Evans behauptete am 30 Aug 2000 um 18:51: > FW_ALLOW_PING_FW="yes" > FW_ALLOW_PING_DMZ="no" > > The following was logged. My hostname and IP changed. > > Aug 27 20:06:14 noname kernel: Packet log: input ACCEPT eth0 PROTO=1 24.8.72.245:8 xxx.yyy.zzz.www:0 L=36 S=0x00 I=56281 F=0x0000 T=118 (#6) You probably missed the "PROTO=1" bit of that line. Have a look at /etc/protocols: icmp 1 ICMP # internet control message protocol So you are not experiencing tcp connection attempts on port 8, but ICMP requests. Looking further: $ grep 8 /usr/i486-glibc20-linux/include/netinet/ip_icmp.h [...] #define ICMP_ECHO 8 /* Echo Request */ [...] So what you are experiencing are simple pings... Bye, Bastian -- Bastian Friedrich bastian(a)bastian-friedrich.de Adress & Fon available on my HP http://www.bastian-friedrich.de/ \~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\ \ Don't hate yourself in the morning - sleep till noon.

1 0

Re: [suse-security] port 8
by Gerry Doris 30 Aug '00

30 Aug '00

Someone from cx280252-a.phnx1.az.home.com (a cable modem user in Phoneix, AZ on the @home network) pinged your host. This is an icmp request (PROTO=1) type 8. It is not an connection attempt on port 8. Nothing to worry about. Gerry On 30 Aug 2000, Russell Evans wrote: > I am running the firewall update for SuSE 6.4 with the following > settings. > > FW_DEV_WORLD="eth0" > FW_DEV_INT="" > FW_DEV_DMZ="" > FW_ROUTE="no" > FW_MASQUERADE="no" > FW_MASQ_NETS="" > FW_MASQ_DEV="$FW_DEV_WORLD" > FW_PROTECT_FROM_INTERNAL="yes" > FW_AUTOPROTECT_GLOBAL_SERVICES="yes" > FW_SERVICES_EXTERNAL_TCP="22 53 110 25" > FW_SERVICES_EXTERNAL_UDP="514 53" > FW_SERVICES_DMZ_TCP="" > FW_SERVICES_DMZ_UDP="" > FW_SERVICES_INTERNAL_TCP="" > FW_SERVICES_INTERNAL_UDP="" > FW_TRUSTED_NETS="" > FW_SERVICES_TRUSTED_TCP="" > FW_SERVICES_TRUSTED_UDP="" > FW_ALLOW_INCOMING_HIGHPORTS_TCP="dns" > FW_ALLOW_INCOMING_HIGHPORTS_UDP="yes" > FW_SERVICE_DNS="yes" > FW_SERVICE_DHCLIENT="no" > FW_SERVICE_DHCPD="no" > FW_FORWARD_TCP="" > FW_FORWARD_UDP="" > FW_REDIRECT_TCP="" > FW_REDIRECT_UDP="" > FW_LOG_DENY_CRIT="yes" > FW_LOG_DENY_ALL="yes" > FW_LOG_ACCEPT_CRIT="yes" > FW_LOG_ACCEPT_ALL="no" > FW_KERNEL_SECURITY="yes" > FW_STOP_KEEP_ROUTING_STATE="no" > FW_ALLOW_PING_FW="yes" > FW_ALLOW_PING_DMZ="no" > FW_ALLOW_FW_TRACEROUTE="no" > FW_ALLOW_FW_SOURCEQUENCH="yes" > FW_MASQ_MODULES="autofw cuseeme ftp irc mfw portfw quake raudio user > vdolive" > > The following was logged. My hostname and IP changed. > > > Aug 27 20:06:14 noname kernel: Packet log: input ACCEPT eth0 PROTO=1 > 24.8.72.245:8 xxx.yyy.zzz.www:0 L=36 S=0x00 I=56281 F=0x0000 T=118 > (#6) > > > Is this a hole in the firewall setup? I do not have the experience to > know. > > Thank you > Russell > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: suse-security-unsubscribe(a)suse.com > For additional commands, e-mail: suse-security-help(a)suse.com > Gerry "The lyf so short, the craft so long to learne" Chaucer

1 0

user masquerade in postfix
by Arndt Groll 30 Aug '00

30 Aug '00

hello, does anybody know what i must do or insert in main.cf to masquerade a user in the address of user(a)firma.de? i have read many about domain masquarde, but i'm not able to find something about user masquarde - by the way - i know how this can be made in qmail but i want do that in postfix. is it support by postfix or must i play with perl? A. Groll

2 1

Relaying with Authentification, Secure Password transmission
by Boris Kantwerk 29 Aug '00

29 Aug '00

Hi *! How do I tell sendmail, to relay mails for all users sending a correct login and password independent from the host from which they send the mail? Additional I want to enable secure password transmission for sendmail, popper and ftpd and don't know how! Thanx, Boris.

5 4