Image
 
linkedin_logo.png rss_logo.jpg
twitter_logo.png youtube_logo.jpg
Latest Additions
 
EH-Net Login
Welcome Guest.






Lost Password?
No account yet? Register
Who's Online
We have 41 guests online
 
Advertisement

You are here: Home arrow Ethical Hacking Discussions and Related Certificationsarrow Web Applicationsarrow XSS Filter Died?
EH-Net
May 19, 2013, 01:59:27 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Go back to The Ethical Hacker Network Online Magazine Home Page
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: XSS Filter Died?  (Read 2353 times)
0 Members and 1 Guest are viewing this topic.
unicityd
Full Member
***
Offline Offline

Posts: 156

Bored IT Manager, Crypto Nerd


View Profile WWW
« on: January 14, 2012, 12:38:16 AM »

I'm trying to figure out what happened to a web app I was testing today.  I was blackbox testing the forum/discussion feature for an online learning app (written in Java) that allows users to post HTML, but has an XSS filter to block known bad HTML tags.  I've found some ways to bypass this particular filter before and was testing some new things today.  When I input something it doesn't like, I would get an error message like: "Forbidden Content: <evil>Boo</evil>"

Here's the strange part: at some point in my testing, it stopped blocking anything at all.  All of the things that it used to flag as "forbidden content" were allowed through.  I could use any tag I wanted including the obvious <script>.  What would cause this?

One guess is that that the routine is throwing an exception and that the exception is handled by simply returning as if everything is okay, but I don't know why it would do that every time.  Would there be a reason for it to maintain state?  If it does, I could see it getting so screwed up that it can't run without throwing an exception.

Is there something else it could be doing?  I don't have source code to check this and I've never run into a similar error while coding.

Thanks,

Unicityd
Logged

BS in IT, CISSP, MS in IS Management (in progress)
cd1zz
Hero Member
*****
Offline Offline

Posts: 561


View Profile WWW
« Reply #1 on: January 14, 2012, 01:21:36 AM »

Sounds like you were whitelisted, mid-test....was that not in the original project specs? You sure the sales guy didn't add it after the PT began?!
Logged

unicityd
Full Member
***
Offline Offline

Posts: 156

Bored IT Manager, Crypto Nerd


View Profile WWW
« Reply #2 on: January 14, 2012, 03:07:51 AM »

It wasn't part of a pen-test, just some independent research.  I'm the application admin for the system which is hosted by the vendor.  As far as I know, there isn't a way to turn the filter off (on purpose).

It's a production system, but school is out right now so I'm pretty much the only persson on.  I've always felt comfortable playing with XSS using a test course where there aren't any real users that I can harm.  The side effects I saw today surprised me.
Logged

BS in IT, CISSP, MS in IS Management (in progress)
MaXe
Hero Member
*****
Offline Offline

Posts: 669


I've just upgraded myself to a cyborg muahahaa!!1


View Profile WWW
« Reply #3 on: January 14, 2012, 01:31:36 PM »

Sounds like Java mischief to me hehe  Grin Somehow you either got whitelisted, or disabled the "Anti-XSS Firewall" or whatever happened. You will only be able to know if you debug the application and reproduce your steps, on another IP with fresh (new) cookies too of course.
Logged

I'm an InterN0T'er
unicityd
Full Member
***
Offline Offline

Posts: 156

Bored IT Manager, Crypto Nerd


View Profile WWW
« Reply #4 on: January 14, 2012, 03:02:49 PM »

Quote
You will only be able to know if you debug the application

I think I'm out of luck since I don't have the ability to debug this app.  I do know that it's a global issue since the problem persists on other accounts/machines.  I really wish I had source code so I could see what the hell they are doing.
Logged

BS in IT, CISSP, MS in IS Management (in progress)
MaXe
Hero Member
*****
Offline Offline

Posts: 669


I've just upgraded myself to a cyborg muahahaa!!1


View Profile WWW
« Reply #5 on: January 14, 2012, 05:08:55 PM »

It would indeed be interesting to see how on earth such a scenario could be possible, as even I haven't seen it elsewhere. I've seen the opposite, that after like 100 attempts you get blacklisted for a while or permanently, but getting whitelisted out of nowhere allowing all script execution vectors, now that's rare but fun to hear about hehe  Grin
Logged

I'm an InterN0T'er
unicityd
Full Member
***
Offline Offline

Posts: 156

Bored IT Manager, Crypto Nerd


View Profile WWW
« Reply #6 on: January 15, 2012, 03:41:19 PM »

I screwed up Sad  I was using multiple test accounts and I mixed up and made one of the accounts a professor instead of a student.

So, the XSS filter functions although I can still bypass it using certain tags.

I would like to know why it blew away a discussion category though; definitely some data corruption at play there.
Logged

BS in IT, CISSP, MS in IS Management (in progress)
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.051 seconds with 23 queries.
 
Exclusive Deal

sansfire13_245x90_cw90.jpg
SANSFIRE 2013
June 15 - 22

5% Off w/ Code: EHN_5

SANS Deals 4 EH-Netters
5% OFF Any SANS Course in Any Format!
Coupon Code: EHN_5 Including SANS Rocky Mountain 2013 & SANS Boston 2013
Polls
Compared to this year, 2013 will be:
 
Recent Forum Topics
EH-Net News Feeds
Latest Additions
 
         
Advertisement

© 2013 The Ethical Hacker Network
Joomla! is Free Software released under the GNU/GPL License.