Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Web-App-Sec
[Top] [All Lists]

Re: XSS Testing

Subject: Re: XSS Testing
Date: Tue, 21 Sep 2004 00:18:35 +0530
On 17/09/04 15:26 +0000, PenTest Guy wrote:
I'm testing a web application.  Previously, I had found XSS using a standard 
variant: <scr1pt>al3rt('XSS')</scr1pt> (note used 3 for e and 1 for i as to 
not cause any problems).  I also URL encoded this same variant and it worked 
as well.  So I told them how to fix it (filtering out malicious characters, 
encoding, etc. on the server side) and it seems fixed now.  I was just 
curious if there is any other way to manipulate the same variant, such as 
other encoding schemes, that might bypass the protections I recommended.


Oh, lots. Why not do the right thing and block by default? Have a set of
valid character sets, and allow only a limited set of valid characters
in there?

Devdas Bhagat

<Prev in Thread] Current Thread [Next in Thread>