[19413] in bugtraq

home help back first fref pref prev next nref lref last post

Re: Orange Web Server v2.1 DoS

daemon@ATHENA.MIT.EDU (bert hubert)
Wed Feb 28 02:28:23 2001

Mail-Followup-To: BUGTRAQ@SECURITYFOCUS.COM
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID:  <20010228011134.B10042@home.ds9a.nl>
Date:         Wed, 28 Feb 2001 01:11:34 +0100
Reply-To: bert hubert <ahu@DS9A.NL>
From: bert hubert <ahu@DS9A.NL>
To: BUGTRAQ@SECURITYFOCUS.COM
In-Reply-To:  <20010227045046.15749.qmail@securityfocus.com>; from
              slipy@B10Z.NET on Tue, Feb 27, 2001 at 04:50:46AM -0000

On Tue, Feb 27, 2001 at 04:50:46AM -0000, slipy@B10Z.NET wrote:

> invalid page fault. This is a very strange DoS, see
> example.

> echo "GET A" | telnet 192.168.0.20 80
>
> ^^ = That simple echo & pipe will cause this:
>
> ORANGEWEBSERVER caused an invalid page fault

This DoS is not so very strange, I've seen it a few times before. When
closing a TCP/IP connection very quickly after creating it, it is possible
for a server to try to send data to a closed connection repeatedly without
proper error checking (people don't expect a connection to die instantly
after it was created).

Under UNIX, you can catch or ignore SIGPIPE as a stopgap solution. Windows
will probably have something similar.

Regards,

bert

--
http://www.PowerDNS.com      Versatile DNS Services
Trilab                       The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet

home help back first fref pref prev next nref lref last post