WebApp Sec mailing list archives
Fixing XSS Vulns
From: "wilsonc" <wilsonc () mantech-wva com>
Date: Fri, 12 Aug 2005 09:41:09 -0400
I'm a new developer to a project, and I've found that our web app is wide open for XSS exploits. (thankfully, its not in production use). I'm not a security expert, but I did some googling and found that the standard procedure is basically to "encode" the string before displaying it to the user, so that specific characters are transformed into their HTML 'escape sequence'. For example, the left paren, '(' would be encoded to be ( A more experience developer has suggested that instead of writing a function to do this when we display, we write a trigger to encode/filter on capture. I explained to him that it would be that HTML-specific 'escape sequences' would then be stored in the database, and what I learned from googling. He feels confident that our data will only be displayed through a web app, and not through any kind of reporting module, and he feels the trigger to encode text is a cleaner implementation. Assuming your data was only going to be displayed back to the user via the same website that captured the input, is there anything wrong with encoding the string on capture? --CW
Current thread:
- Fixing XSS Vulns wilsonc (Aug 12)
- Re: Fixing XSS Vulns Petko Petkov (Aug 12)
- Re: Fixing XSS Vulns RSnake (Aug 12)
- Re: Fixing XSS Vulns Tim (Aug 12)
- Re: Fixing XSS Vulns Stephen de Vries (Aug 12)
- RE: Fixing XSS Vulns yeesan wong (Aug 14)
- <Possible follow-ups>
- RE: Fixing XSS Vulns Smith, Johnathon (KEYPEOPLE RESOURCES INC) (Aug 12)
- Re: Fixing XSS Vulns Steven M. Christey (Aug 12)
- Re: Fixing XSS Vulns Tim (Aug 13)
- RE: Fixing XSS Vulns Jeff Robertson (Aug 12)
- RE: Fixing XSS Vulns Cyrill Osterwalder (Aug 15)