Date Discovered October 8, 2002
Description Reportedly, the server hosting sendmail, ftp.sendmail.org, was compromised recently. It has been reported that the intruder made modifications to the source code of sendmail to include Trojan Horse code. Downloads of the sendmail source code from ftp.sendmail.org between September 28, 2002 and October 6, 2002 likely contain the trojan code.
It has also been reported that versions of sendmail available via HTTP distribution on the Sendmail Consortium site are not affected.
Reports say that the trojan will run once upon compilation of sendmail. Once the Trojan is executed, it attempts to connect to host spatula.aclue.com (188.8.131.52) on port 6667.
Although unconfirmed, it has been reported that the service listening on port 6667 of host spatula.aclue.com (184.108.40.206) has been disabled.
The Sendmail Consortium has signed all valid distributions of the sendmail software with the following PGP key:
pub 1024R/678C0A03 2001-12-18 Sendmail Signing Key/2002 <sendmail@Sendmail.ORG>
Key fingerprint = 7B 02 F4 AA FC C0 22 DA 47 3E 2A 9A 9B 35 22 45
Additionally, the following checksums have been made available to verify packages against:
- Sendmail Consortium Sendmail 8.12.6
Block external access at the network boundary, unless external parties require service. Filter untrusted network traffic at border routers and network firewalls.
Run all software as a nonprivileged user with minimal access rights.
Perform all tasks with the minimal privileges possible to perform task.
The vendor has stated that the versions served via HTTP download are not affected, and the valid versions of sendmail for downloaded from http://www.sendmail.org. They are available from the normal distribution channels and have the following MD5 checksums:
Additionally, they are signed with the Sendmail Consortium PGP Key.
Credits Advisory released by CERT.
Copyright © Symantec Corporation.
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and firstname.lastname@example.org
are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.