|
Jun
14
2
|
XSS for Lunch - Yum! |
|||||
I was reading SEO Black Hat during my lunch break, and it pointed me to RSnake's article on using GreaseMonkey to sniff out XSS attack vulnerabilities. Since I'm a white hat SEO, I'll pretend I'm only interested in this stuff to the extent of attack prevention, so I added a few things to his proof of concept to make it more usable for that purpose (or any purpose, really). First, we create a script that utilizes the last code-snippet I posted here that parses out the response codes from a HTTP document (LinkChecker.php), located here. <? We name the file "xss_detect.php." Then we modify RSnake's script with a few little features that make it much more usable casually. We insert an image for various response codes, and a bright yellow one for a 301. If you see a 301, you know it's an oppor … nerability. Here is the modified script: // ==UserScript== (function() { Here's one example of a big fat vulnerability:
Here's a link to my site from theirs: I left this script activated in greasemonkey, and I will be auditing all my sites this way. Related posts: Checking for Dead Links Automatically This neat little class can return the HTTP status code... Auditing for HTML Tainting Note: the code for the auditing script is located here....
| ||||||
"2 Wise Comments Banged Out Somewhere On The Internet ..."
hi jamie, ha.ckers.org security lab - Archive » SEO redirects continued[...] Jaimie Sirovich just posted an ammendment to my post about SEO redirection on his blog. His post expounds on my crappy SEO redirection explanation by adding in the loggin script, making it more customizable and in general less lame. His is better, check it out. I think this really is a huge problem that will stay around for quite a while. I started finding these in Google a while back, and then they came fast and furious. [...]
|



















