Running from a single machine will hardly - if ever- constitute a real
threat in terms of trying to induce a DOS style attack (eg. take the site
off the net) - these generally have to use multiple sites all synchronously
targeting a single point of attack (eg. SYN flood and normal synchronous
page requests). The reason being that you will be limited by your own
bandwidth before you even touch that of a commercial site.
The real possibility is that you might be able to hack into a site and
compromise it's security by means of either a webserver hole (or
vulnerability), SQL injection (a real threat which can be overcome by simply
using stored procedures or being very very careful with the SQL statements)
or auto-incrementing counters that don't use GUIDs allowing someone to
predict or reuse existing and new session / user identifiers.
There will be more but in general terms the three 'real' hack modes
mentioned are the most common and certainly the easiest to secure against.
Chris.
I have done tests for form hacking and ASP.
I can use IE to save a page locally, which has a form, to the hard
drive (file/save) then change the "action" property to the qualified
url and submit the form.
The action page picks up the POST or GET http string and works with
it...
Can anyone expound on a BEST PRACTICE for eliminating hacks in this
scenario...
I will expound on my findings as everyone else does.
Thanks.
For instance, I wrote this with VB (could be script too with minor
modifications, but I wanted to step debug, etc...) anyway, here's
some code where [word from dictionary] could be a word in websters
which changes every iteration in the loop which would function as a
"brute force" attack. OR this loop could be used just to screw the
site up and use up resources if left to loop:
Sub httphack()
'Note either of the objects below could work
'Dim myReq As MSXML2.XMLHTTP30
'Set myReq = New MSXML2.XMLHTTP30
Dim myReq As WinHttpRequest
Set myReq = New WinHttpRequest
Dim strBody As String
For hackCount = 1 To 10000000000
myReq.Open "POST", "
http://srv2000asrx2/testhack/handler.asp", False
myReq.SetRequestHeader
"Content-Type","application/x-www-form-urlencoded"
myReq.SetRequestHeader "REFERER", "[whatever]"
myReq.Option(WinHttpRequestOption_EnableRedirects) = True
strBody = "username=[word from dictionary]&password=[word from
dictionary]"
myReq.Send strBody
res = myReq.ResponseText
if res <> [the typical error return or page text] THEN
[it must be a redirect or something]
[save the user name and password and try to log in with them]
end if
Next
End Sub
HANDLER.ASP file:
<%=response.write(request.form("username")%>
<%=response.write(request.form("password")%>
END HANDLER.ASP file
Please comment on the general threat of this simple code... I have
several ideas about protecting against it, but I'm interested in
various input at this time... go ahead and try it out if you have VB
or adapt it to script and try it. I'm currently building an
e-commerce web site and I'm very worried about this type of threat.