Date: Wed, 5 Jul 2000 16:04:15 -0700 (PDT) From: FreeBSD Security Advisories <security-advisories@freebsd.org> Subject: FreeBSD Ports Security Advisory: FreeBSD-SA-00:26.popper Message-ID: <20000705230415.3BA5A37BCFB@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
=============================================================================
FreeBSD-SA-00:26 Security Advisory
FreeBSD, Inc.
Topic: popper port contains remote vulnerability
Category: ports
Module: popper
Announced: 2000-07-05
Credits: Prizm <prizm@RESENTMENT.ORG>
Affects: Ports collection.
Corrected: 2000-05-25
Vendor status: Notified
FreeBSD only: NO
I. Background
QPopper is a popular POP3 mail server.
II. Problem Description
The popper port, version 2.53 and earlier, incorrectly parses string
formatting operators included in part of the email message header. A
remote attacker can send a malicious email message to a local user
which can cause arbitrary code to be executed on the server when a POP
client retrieves the message using the UIDL command. The code is
executed as the user who is retrieving mail: thus if root reads email
via POP3 this can lead to a root compromise.
The popper port is not installed by default, nor is it "part of
FreeBSD" as such: it is part of the FreeBSD ports collection, which
contains over 3400 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, but it was fixed in
time for FreeBSD 3.5.
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 cause arbitrary code to be executed as the retrieving
user when a POP client retrieves email.
If you have not chosen to install the popper port/package, then
your system is not vulnerable to this problem.
IV. Workaround
Deinstall the popper port/package, if you you have installed it.
V. Solution
One of the following:
1) Upgrade your entire ports collection and rebuild the popper port.
2) Deinstall the old package and install a new package dated after the
correction date, obtained from:
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-3-stable/mail/popper-2.53.tar.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-4-stable/mail/popper-2.53.tar.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-4-stable/mail/popper-2.53.tar.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-5-current/mail/popper-2.53.tar.gz
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/alpha/packages-5-current/mail/popper-2.53.tar.gz
3) download a new port skeleton for the popper 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
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBOWGoqFUuHi5z0oilAQGhvAP/adBX2Q7H4quBw3rY6fPNNGJtwkxsNRem
11hCXzkEHDkX5bARzNwnWzS/BNz9PFxdw524ukOtEevR/lLfI1kyhXepA5G4gtPr
aujSw/eHi5ts7++gPhybT3abva1dLwbnaFjYaSjxFGjkMH8vk+/ZheqnIKX7fC50
kEr7c1JoaUA=
=0y6/
-----END PGP SIGNATURE-----
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000705230415.3BA5A37BCFB>