[<prev] [next>] [day] [month] [year] [list]
Message-ID: <OpenPKG-SA-2004.020__37187.4453303919$1084037690@openpkg.org>
Date: Fri, 7 May 2004 22:01:55 +0200
From: OpenPKG <openpkg@...npkg.org>
To: bugtraq@...urityfocus.com
Subject: [OpenPKG-SA-2004.020] OpenPKG Security Advisory (ssmtp)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
________________________________________________________________________
OpenPKG Security Advisory The OpenPKG Project
http://www.openpkg.org/security.html http://www.openpkg.org
openpkg-security@...npkg.org openpkg@...npkg.org
OpenPKG-SA-2004.020 07-May-2004
________________________________________________________________________
Package: ssmtp
Vulnerability: denial of service, code execution
OpenPKG Specific: no
Affected Releases: Affected Packages: Corrected Packages:
OpenPKG CURRENT <= ssmtp-2.48-20040207 >= ssmtp-2.60.8-20040507
OpenPKG 2.0 <= ssmtp-2.48-2.0.0 >= ssmtp-2.48-2.0.1
OpenPKG 1.3 <= ssmtp-2.48-1.3.0 >= ssmtp-2.48-1.3.1
Dependent Packages: none
Description:
Two format string bugs were discovered in sSMTP [1], a simple
sending-only Mail Transport Agent (MTA). Untrusted values in the
functions die() and log_event() were passed to printf(3)-like
functions as format strings. These vulnerabilities could potentially
allow remote mail relays to cause a Denial of Service (DoS) and
possibly execute arbitrary code. The Common Vulnerabilities and
Exposures (CVE) project assigned the id CAN-2004-0156 [2] to the
problem.
Please check whether you are affected by running "<prefix>/bin/rpm -q
ssmtp". If you have the "ssmtp" package installed and its version is
affected (see above), we recommend that you immediately upgrade it
(see Solution) [3][4].
Solution:
Select the updated source RPM appropriate for your OpenPKG release
[5][6], fetch it from the OpenPKG FTP service [7][8] or a mirror
location, verify its integrity [9], build a corresponding binary RPM
from it [3] and update your OpenPKG installation by applying the
binary RPM [4]. For the most recent release OpenPKG 2.0, perform the
following operations to permanently fix the security problem (for
other releases adjust accordingly).
$ ftp ftp.openpkg.org
ftp> bin
ftp> cd release/2.0/UPD
ftp> get ssmtp-2.48-2.0.1.src.rpm
ftp> bye
$ <prefix>/bin/openpkg rpm -v --checksig ssmtp-2.48-2.0.1.src.rpm
$ <prefix>/bin/openpkg rpm --rebuild ssmtp-2.48-2.0.1.src.rpm
$ su -
# <prefix>/bin/openpkg rpm -Fvh <prefix>/RPM/PKG/ssmtp-2.48-2.0.1.*.rpm
________________________________________________________________________
References:
[1] ftp://ftp.debian.org/debian/pool/main/s/ssmtp/
[2] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2004-0156
[3] http://www.openpkg.org/tutorial.html#regular-source
[4] http://www.openpkg.org/tutorial.html#regular-binary
[5] ftp://ftp.openpkg.org/release/1.3/UPD/ssmtp-2.48-1.3.1.src.rpm
[6] ftp://ftp.openpkg.org/release/2.0/UPD/ssmtp-2.48-2.0.1.src.rpm
[7] ftp://ftp.openpkg.org/release/1.3/UPD/
[8] ftp://ftp.openpkg.org/release/2.0/UPD/
[9] http://www.openpkg.org/security.html#signature
________________________________________________________________________
For security reasons, this advisory was digitally signed with the
OpenPGP public key "OpenPKG <openpkg@...npkg.org>" (ID 63C4CB9F) of the
OpenPKG project which you can retrieve from http://pgp.openpkg.org and
hkp://pgp.openpkg.org. Follow the instructions on http://pgp.openpkg.org/
for details on how to verify the integrity of this advisory.
________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Comment: OpenPKG <openpkg@...npkg.org>
iD8DBQFAm+sHgHWT4GPEy58RAoFBAKC9kbFPY0qTlByig5Wn1Ap0SLzGegCdGsJM
/GRUxOM0aISYf8fbvxpPqlc=
=JXhQ
-----END PGP SIGNATURE-----
Powered by blists - more mailing lists