bugtraq - resources consumption in DiGi WWW Server

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20040427173643.17B9D2431C@chernobyl.investici.org>
Date: Tue, 27 Apr 2004 17:36:43 -0000
From: "Donato Ferrante" <fdonato@...istici.org>
To: <bugtraq@...urityfocus.com>
Subject: resources consumption in DiGi WWW Server

                           Donato Ferrante

Application:  DiGi WWW Server
              http://wwwserver.sourceforge.net

Version:      Compieuw.1

Bug:          resources consumption

Date:         27-Apr-2004

Author:       Donato Ferrante
              e-mail: fdonato@...istici.org
              web:    www.autistici.org/fdonato

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

1. Description
2. The bug
3. The code
4. The fix

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

----------------
1. Description:
----------------

Vendor's Description:

"DiGi WWW Server is a webserver. It is easy-to-use but also supports
access control, virtual folders and multiple ports. You can use plugin
dll's to add extra functionality. The server can run as a GUI
application and as an NT service."

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

------------
2. The bug:
------------

The program has a procedure that makes a conversion, it parses the
request strings replacing all the occurrences of slash with backslash.

So if you send to the webserver a crafted big request full of '/',
the server will be freezed by consuming a lot of CPU resources.

Furthermore it's also possible to freeze the server by sending to it a
long http request.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

-------------
3. The code:
-------------

To test the vulnerability, send to the webserver an http request like:

GET /// [ 660 kb of / ] /// HTTP/1.1

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

------------
4. The fix:
------------

Bug fixed in the version Compieuw.2.

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx