Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
Subject: Advisory Code: VIGILANTE-2000011 Lotus Domino ESMTP Service Buffer overflow
From: erik damsgaard (erik.damsgaardVIGILANTE.CON)
Date: Mon Sep 11 2000 - 03:15:25 CDT
- Next message: Lionel Cons: "A new approach to the glibc bugs"
- Previous message: Karl Hanmore: "Unsafe passing of variables to mailform.pl in MailForm V2.0"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Lotus Domino ESMTP Service Buffer overflow
Advisory Code: VIGILANTE-2000011
September 11, 2000
Lotus Domino Release 5.0.2a (Intl) ESMTP Service on OS/2 Warp 4.5
Lotus Domino Release 5.0.2c (Intl) ESMTP Service on OS/2 Warp 4.5
Earlier versions of the ESMTP service can be vulnerable. ESMTP service on
other operating systems can be vulnerable as well. This has not been tested.
When opening a connection to the SMTP service and filling the arguments to
the following commands:
with a buffer of size 4096 chars the service will crash. This is similar to
the “mail from” denial-of-service vulnerability reported in
The service will also crash when the command “mail from” receives an
argument on a size of 4096 chars but that is a known vulnerability.
Lotus Denmark was contacted on the 11th of August. The 29th of August we
received notification regarding a fix.
Fix (quote from the vendor):
“ 5/25/00 fix smtp crash with long mail from. (SPR WAT4KKHUR) Fix is based
on build v504_05192000
6/19/00 More denial of service attack fixes (SPR JSHY4HEV9B) Fix is based on
build v505_05312000 ”
Fix SPR JSHY4HEV9B should be available in the beginning of September.
Please contact Lotus support for information on location on SPR JSHY4HEV9B.
Vendor URL: http://www.lotus.com/
Product URL: http://www.lotus.com/home.nsf/welcome/dominomailserver
Copyright VIGILANTe 2000-08-11
The information within this document may change without notice. Use of
this information constitutes acceptance for use in an AS IS
condition. There are NO warranties with regard to this information.
In no event shall the author be liable for any consequences whatsoever
arising out of or in connection with the use or spread of this
information. Any use of this information lays within the user's
Please send suggestions, updates, and comments to: