US-CERT
Vulnerability
Notes
Database

Search Vulnerability Notes

Vulnerability Notes Help Information
 

 View Notes By
Name

ID Number

CVE Name

Date Public

Date Published

Date Updated

Severity Metric

 Other Documents
Technical Alerts

Technical Bulletins

Alerts

Security Tips

OpenPKG Information for VU#993452

Date Notified:
Date Updated:
Status Summary:Vulnerable

Vendor Statement

Please see the vendor statement for VU#993452 at:

http://www.openpkg.org/security/OpenPKG-SA-2003.037-sendmail.html

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Text of statement for VU#993452 follows:


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

________________________________________________________________________

OpenPKG Security Advisory                            The OpenPKG Project
http://www.openpkg.org/security.html              http://www.openpkg.org
openpkg-security@openpkg.org                         openpkg@openpkg.org
OpenPKG-SA-2003.037                                          28-Aug-2003
________________________________________________________________________

Package:             sendmail
Vulnerability:       Denial of Service
OpenPKG Specific:    no

Affected Releases:   Affected Packages:        Corrected Packages:
OpenPKG CURRENT      none                      N.A.
OpenPKG 1.3          none                      N.A.
OpenPKG 1.2          <= sendmail-8.12.7-1.2.2  >= sendmail-8.12.7-1.2.3

Dependent Packages:  none

Description:
Oleg Bulyzhin reported to FreeBSD [1] a confirmed [2] Denial of
Service (DoS) vulnerability in all version of the Sendmail MTA [0]
earlier than 8.12.9. Due to a wrong initialization of an internal
structure, if Sendmail gets a bad DNS reply (with actual reply size
not equal the announced reply size), it later calls free() on a random
address. This usually cause Sendmail to crash.


Please check whether you are affected by running "<prefix>/bin/rpm
-q sendmail". If you have the "sendmail" 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], fetch it from the OpenPKG FTP service [6] or a mirror location,
verify its integrity [7], build a corresponding binary RPM from it [3]
and update your OpenPKG installation by applying the binary RPM [4].
For the affected release OpenPKG 1.2, perform the following operations
to permanently fix the security problem (for other releases adjust
accordingly).


$ ftp ftp.openpkg.org
ftp> bin
ftp> cd release/1.2/UPD
ftp> get sendmail-8.12.7-1.2.3.src.rpm
ftp> bye
$ <prefix>/bin/rpm -v --checksig sendmail-8.12.7-1.2.3.src.rpm
$ <prefix>/bin/rpm --rebuild sendmail-8.12.7-1.2.3.src.rpm
$ su -
# <prefix>/bin/rpm -Fvh <prefix>/RPM/PKG/sendmail-8.12.7-1.2.3.*.rpm

________________________________________________________________________

References:
[0]
http://www.sendmail.org/
[1]
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/54367
[2]
http://www.sendmail.org/dnsmap1.html
[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.2/UPD/sendmail-8.12.7-1.2.3.src.rpm
[6]
ftp://ftp.openpkg.org/release/1.2/UPD/
[7]
http://www.openpkg.org/security.html#signature
________________________________________________________________________

For security reasons, this advisory was digitally signed with the
OpenPGP public key "OpenPKG <openpkg@openpkg.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@openpkg.org>

iD8DBQE/Tb+ZgHWT4GPEy58RAsYCAJ9ZCxyvh1cHAc3yodParNpttFQlCQCg3Esl
aNgXgF5F2UNtdcjd8JUblII=
=Yd9K
-----END PGP SIGNATURE-----

If you have feedback, comments, or additional information about this vulnerability, please send us email.
 

Produced 2008 by US-CERT, a government organization
Disclaimers and copyright information