Most web app geeks call permanent XSS HTML injection these days.
Now sites that have permanent XSS might also be vulnerable to SSI injection. That is when it becomes a client-to-server attack.
If you are interested you might want to check out the following URLS
http://www.owasp.org/asac/input_validation/css.shtml http://www.cgisecurity.com/articles/xss-faq.shtml
Of course a google search for "Cross Site Scripting" will turn up a bunch of good links as well.
On Wednesday, July 23, 2003, at 03:35 PM, Shanphen Dawa wrote:
So why not show one of these legitimate examples instead of the overused window popup script?
It would just be easier to ascertain the level of severity if an actual DoS string or this "trusted internal call" was exploited.
I am sure there are a lot of forms that can be a victim of a xss string, but how many of them can actually be used for anything useful (from an attacker point of view)?
On Wed, 23 Jul 2003 11:34:53 -0700 "morning_wood" <[EMAIL PROTECTED]> wrote:
both..
Can you use this to DoS the server?consider that the server must process the requests.. i think it can be a
DoS issue with enough length and quanity of the requests.
Can you use this to gain access to areas on the server otherwise notavailable?
many servers assume a call to "/somefolder/somefile.ext" is a trusted internal call. where http://theserver/somefolder/somefile.ext
morning_wood http://exploitlabs.com
-- /* "To avoid all evil, to cultivate good, and to cleanse one's mind this is the teaching of the Buddhas."
Martin Ekendahl http://www.hardlined.com [EMAIL PROTECTED] */ _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.netsys.com/full-disclosure-charter.html
