There is a difference between an exploit of a vulnerability, and tying up network resources.

The Slowloris software has been around since '09, and the attack has been known since well before that. It does not exploit a flaw in faulty code, it merely uses a clever method of leaving open connections. It affects more than just Apache, so it couldn't really be called an exploit, which usually has a fairly specific target.

If, however, you found a flaw in, say, the way Apache frees up old connections (improper memory management, pointer issues, etc) and crafted a special packet or came up with a method to exploit that, I'd call that 0day.

Slowloris affect apache and a few other web servers, but does not affect all of them, such as IIS and NGINX. therefore it is an exploit.

What I have done is made an exploit that does a slowloris type affect via POST requests, and keeping them alive.

This is a 0day, there has been 0days and 0hours since it has been discovered or patched.Exploits are more than just buffer overflows and memory corruption, there is SQLi and XSS 0days, that are just as devastating as this.

Maybe you are just jealous that I made a simple exploit you could have made yourself?

Aha! A variable named Exploit! *Surely* this makes it a bonafide 0day!

In summary: There is nothing about your program that is unique, original, or cool. It is not a 0day. The guy who first discovered the attack and used it, however, did come up with something unique, original, and cool. You are simply applying the same technique. Here, let me demonstrate:

Th3_M4d_H4tt3r wrote:Yes I know what a 0day is, it means there has been 0 days and 0 hours since it has been patched or discovered.

It it is a '1,473' day why does it work perfectly on my fully updated apache web server?

funny.

Evidently you don't know what 0day is. 0 day refers to "days of public disclosure." When it is publicly disclosed, that is day 1. This has already been known for a while. Whether or not it has been patched is a different issue. Also, if you post 0day to HTS, it is no longer 0day because HTS is publicly accessible (google crawls it, for one).

Also, 1337sp34k is pretty much a script kiddie thing these days. (These days being defined as the past 15 or more years.)

Last edited by anonHacker on Sun Aug 25, 2013 1:12 am, edited 1 time in total.

Th3_M4d_H4tt3r wrote:Yes I know what a 0day is, it means there has been 0 days and 0 hours since it has been patched or discovered.

It it is a '1,473' day why does it work perfectly on my fully updated apache web server?

funny.

Evidently you don't know what 0day is. 0 day refers to "days of public disclosure." When it is publicly disclosed, that is day 1. This has already been known for a while. Whether or not it has been patched is a different issue. Also, if you post 0day to HTS, it is no longer 0day because HTS is publicly accessible (google crawls it, for one).

Also, 1337sp34k is pretty much a script kiddie thing these days. (These days being defined as the past 15 or more years.)

I only use 1337sp34k in my usernames, as most of them are already taken.alright I am in rage mode.