From owner-freebsd-security-notifications Wed May 17 14:37: 5 2000 Delivered-To: freebsd-security-notifications@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id B2AC537BCC0; Wed, 17 May 2000 14:36:49 -0700 (PDT) From: FreeBSD Security Officer Subject: FreeBSD Security Advisory: FreeBSD-SA-00:08.lynx [REVISED] From: FreeBSD Security Officer Message-Id: <20000517213649.B2AC537BCC0@hub.freebsd.org> Date: Wed, 17 May 2000 14:36:49 -0700 (PDT) Sender: owner-freebsd-security-notifications@FreeBSD.ORG Precedence: bulk Reply-To: postmaster@freebsd.org X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-00:08 Security Advisory FreeBSD, Inc. Topic: Lynx ports contain numerous buffer overflows Category: ports Module: lynx/lynx-current/lynx-ssl/ja-lynx/ja-lynx-current Announced: 2000-03-15 Revised: 2000-05-17 Affects: Ports collection before the correction date. Corrected: 2000-04-16 [lynx-current] 2000-04-21 [lynx] FreeBSD only: NO I. Background Lynx is a popular text-mode WWW browser, available in several versions including SSL support and Japanese language localization. II. Problem Description Versions of the lynx software prior to version 2.8.3pre.5 were written in a very insecure style and contain numerous potential and several proven security vulnerabilities (publicized on the BugTraq mailing list) exploitable by a malicious server. The lynx ports are not installed by default, nor are they "part of FreeBSD" as such: they are part of the FreeBSD ports collection, which contains over 3200 third-party applications in a ready-to-install format. FreeBSD makes no claim about the security of these third-party applications, although an effort is underway to provide a security audit of the most security-critical ports. III. Impact A malicious server which is visited by a user with the lynx browser can exploit the browser security holes in order to execute arbitrary code as the local user. If you have not chosen to install any of the lynx/lynx-current/lynx-ssl/ja-lynx/ja-lynx-current ports/packages, then your system is not vulnerable. IV. Workaround Remove the lynx/lynx-current/lynx-ssl/ja-lynx/ja-lynx-current ports, if you you have installed them. V. Solution Upgrade to lynx or lynx-current after the correction date. After the initial release of this advisory, the Lynx development team conducted an audit of the source code, and have corrected the known vulnerabilities in lynx as well as increasing the robustness of the string-handling code. As of lynx-2.8.3pre.5, we consider it safe enough to use again. Note that there may be undiscovered vulnerabilities remaining in the code, as with all software - but should any further vulnerabilities be discovered a new advisory will be issued. At this time the lynx-ssl/ja-lynx/ja-lynx-current ports are not yet updated to a safe version of lynx: this advisory will be reissued again once they are. 1) Upgrade your entire ports collection and rebuild the lynx or lynx-current port. 2) Reinstall a lynx new package dated after the correction date, obtained from: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/www/lynx-2.8.3.1.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/www/lynx-2.8.3.1.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-4-stable/www/lynx-2.8.3.1.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/www/lynx-2.8.3.1.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-5-current/www/lynx-2.8.3.1.tgz Note that the lynx-current port is not automatically built as a package. 3) download a new port skeleton for the lynx/lynx-current port from: http://www.freebsd.org/ports/ and use it to rebuild the port. 4) Use the portcheckout utility to automate option (3) above. The portcheckout port is available in /usr/ports/devel/portcheckout or the package can be obtained from: ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/devel/portcheckout-1.0.tgz VI. Revision History v1.0 2000-03-15 Initial release v1.1 2000-05-17 Update to note fix of lynx and lynx-current ports. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOSMQT1UuHi5z0oilAQHlgwP9EiLqvf8MM55fvftEXPMfL6PJ6HFQPYMH +TqX5Q/P9s0mgBFiGfN8wblmtEUyZ1GwF8goPa9fqqJIfNg8Qu2zWqJOYPjc20hW yo3Rxbi+lEWOYxLpxBKDhvBH7yWxiV8Nm1+w73a76BjaZ20E0b91hgw2lebFiZPi uzK38WjnFNQ= =qWEC -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security-notifications" in the body of the message From owner-freebsd-security-notifications Wed May 17 14:39:59 2000 Delivered-To: freebsd-security-notifications@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2DC8137BCDE; Wed, 17 May 2000 14:39:50 -0700 (PDT) From: FreeBSD Security Officer Subject: FreeBSD Security Advisory: FreeBSD-SA-00:18.gnapster [REVISED] From: FreeBSD Security Officer Message-Id: <20000517213950.2DC8137BCDE@hub.freebsd.org> Date: Wed, 17 May 2000 14:39:50 -0700 (PDT) Sender: owner-freebsd-security-notifications@FreeBSD.ORG Precedence: bulk Reply-To: postmaster@freebsd.org X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- ============================================================================= FreeBSD-SA-00:18 Security Advisory FreeBSD, Inc. Topic: gnapster/knapster ports allows remote users to view local files Category: ports Module: gnapster/knapster Announced: 2000-05-09 Reissued: 2000-05-16 Credits: Fixed by vendor. Knapster vulnerability pointed out by: Tom Daniels via BugTraq Affects: Ports collection. Corrected: 2000-04-29 (gnapster) 2000-05-01 (knapster) Vendor status: Updated version released. FreeBSD only: NO I. Background Gnapster and knapster are clients for the Napster file-sharing network. II. Problem Description The gnapster port (version 1.3.8 and earlier), and the knapster port (version 0.9 and earlier) contain a vulnerability which allows remote napster users to view any file on the local system which is accessible to the user running gnapster/knapster. Gnapster and knapster do not run with elevated privileges, so it is only the user's regular filesystem access permissions which are involved. Note that there may be further undiscovered bugs in these and other napster clients leading to a similar vulnerability. System administrators and users should exercise discretion in installing a napster client on their system. The gnapster/knapster ports are not installed by default, nor are they "part of FreeBSD" as such: they are part of the FreeBSD ports collection, which contains over 3200 third-party applications in a ready-to-install format. The ports collection shipped with FreeBSD 4.0 contains this problem since it was discovered after the release. FreeBSD makes no claim about the security of these third-party applications, although an effort is underway to provide a security audit of the most security-critical ports. III. Impact Remote users can view files accessible to the user running the gnapster/knapster client. If you have not chosen to install a napster client, then your system is not vulnerable to this problem. IV. Workaround Deinstall the gnapster and/or knapster port/package, if you you have installed them. V. Solution One of the following: 1) Upgrade your entire ports collection and rebuild the gnapster and/or knapster port. 2) Reinstall a new package dated after the correction date, obtained from: [gnapster] ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/audio/gnapster-1.3.9.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/audio/gnapster-1.3.9.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-4-stable/audio/gnapster-1.3.9.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/audio/gnapster-1.3.9.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-5-current/audio/gnapster-1.3.9.tgz [knapster] ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/audio/knapster-0.10.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/audio/knapster-0.10.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-4-stable/audio/knapster-0.10.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/audio/knapster-0.10.tgz ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-5-current/audio/knapster-0.10.tgz 3) download a new port skeleton for the gnapster/knapster ports from: http://www.freebsd.org/ports/ and use it to rebuild the port(s). 4) Use the portcheckout utility to automate option (3) above. The portcheckout port is available in /usr/ports/devel/portcheckout or the package can be obtained from: ftp://ftp.freebsd.org/pub/FreeBSD/ports/packages/devel/portcheckout-1.0.tgz VI. Revision History v1.0 2000-05-09 Initial release v1.1 2000-05-16 Update to note that knapster 0.9 is also vulnerable and broaden warning to include all napster clients. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOSMRPVUuHi5z0oilAQHclAP/X+2Xdki6PUEZ/fCHdwZTLEC0kQNenOJ9 oWxWFuI4z3jpylQ3CweIoo9akx32ZzyIVHTViG3mF2BC+NRQShl1aXu2MYqy6vKc c4R+oHxx2OeYSQo4Q8rS8Ttxa543ynXg9wLBL0vtGMq07GtVYTXpg1+Ooi+QKe2o 9JMpcxAohAQ= =2iHQ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security-notifications" in the body of the message