Mercury Mail Transport System multiple IMAP command buffer overflow

mercury-command-bo (18318) The risk level is classified as LowLow Risk

Description:

Mercury Mail Transport System is vulnerable to a denial of service attack, caused by a buffer overflow when handling certain commands. By supplying a specially-crafted command, such as: EXAMINE, SUBSCRIBE, STATUS, APPEND, CHECK, CLOSE, EXPUNGE, FETCH, DELETE, RENAME, LIST, SEARCH, CREATE and UNSUBSCRIBE, a remote attacker could overflow the buffer and cause the server to crash.

Platforms Affected:

  • Pmail, Mercury Mail Transport System 4.01a

Remedy:

No remedy available as of February 16, 2009.

Consequences:

Denial of Service

References:

  • Full-Disclosure Mailing List, Wed Dec 01 2004 - 15:16:50 CST , Multiple buffer overflows exist in Mercury/32, v4.01a, Dec 8 2003. at http://archives.neohapsis.com/archives/fulldisclosure/2004-12/0028.html.
  • Pmail Web site, Mercury Mail Transport System, Windows version - Features at http://www.pmail.com/overviews/ovw_mercwin.htm.
  • BID-11775: Mercury Mail Multiple Remote IMAP Stack Buffer Overflow Vulnerabilities
  • CVE-2004-1211: Multiple buffer overflows in the IMAP service in Mercury/32 4.01a allow remote authenticated users to cause a denial of service (application crash) and possibly execute arbitrary code via long arguments to the (1) EXAMINE, (2) SUBSCRIBE, (3) STATUS, (4) APPEND, (5) CHECK, (6) CLOSE, (7) EXPUNGE, (8) FETCH, (9) RENAME, (10) DELETE, (11) LIST, (12) SEARCH, (13) CREATE, or (14) UNSUBSCRIBE commands.
  • SA13348: Mercury Mail Transport System Command Handling Buffer Overflows

Reported:

Dec 01, 2004

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

Return to the main page