Cobalt RaQ3 poprelayd allows mail relay using SMTP
| cobalt-poprelayd-mail-relay (6806) |  Medium Risk |
Description:
Cobalt RaQ3 Server could allow a remote attacker to perform mail relaying on the system, caused by a vulnerability in the poprelayd daemon. The poprelayd daemon fails to properly check the /var/log/maillog file output. This allows a remote attacker to create a specially-crafted string in the log file to perform mail relaying while using the SMTP server.
Consequences:
Bypass Security
Remedy:
Update poprelayd to the latest version, or at least apply Poprelayd 2.0-5 Update 4.0.1 (RaQ3-All-Security-4.0.1-10628.pkg) as described on the Sun Cobalt RaQ3 Downloads page. See References.
Sun Cobalt has also made experimental patches available for poprelayd-2.0-4, which can be applied to /usr/local/sbin/poprelayd to correct the relay exploit. See References.
References:
- BugTraq Mailing List, Mon Jul 09 2001 - 14:03:06 CDT: Re: poprelayd and sendmail relay authentication problem (Cobalt Raq3).
- BugTraq Mailing List, Tue Jul 03 2001 - 12:05:10 CDT: poprelayd and sendmail relay authentication problem (Cobalt Raq3).
- BID-2986: Cobalt Raq3 PopRelayD Arbitrary SMTP Relay Vulnerability
- CVE-1999-0512: A mail server is explicitly configured to allow SMTP mail relay, which allows abuse by spammers.
- CVE-2001-1075: poprelayd script before 2.0 in Cobalt RaQ3 servers allows remote attackers to bypass authentication for relaying by causing a POP login by user string that includes the attacker's IP address to be injected into the maillog log file.
Platforms Affected:
- Sun Cobalt RaQ 3
Reported:
Jul 03, 2001
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net