I would like to emphasise reading "Understanding the cause and effect of CSS (XSS) Vulnerabilities " at http://www.technicalinfo.net/papers/CSS.html as recommended previously by Dave Watts.
If you weren't paranoid about XSS before reading this article you might be after! Besides the obvious dangers of unrestricted form input there is also inline scripting where malicious code is used in the url.
One could pass all urls (#cgi.script_name##cgi.query_string#) through a tag like CF_codecleaner (available at Macromedia.com). However all we need to establish is whether there are "naughty bits" in the url so a quick
CompareNoCase(attributes.input,cleaned_input)
(to compare original url+query string with the cleansed url+querystring)
is all one needs. I roughed up a quick mod to cf_codecleaner to do this and it takes 15 milliseconds to check the url. If the url is "unacceptable" you can then email yourself the details and cflocation to google etc!
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- Re: Securing CF Apps against SQL Injection & Cross Si... Andrew Grosset
- Re: Securing CF Apps against SQL Injection & Cro... Andrew Grosset
- Re: Securing CF Apps against SQL Injection & Cro... Matt Robertson
- Re: Securing CF Apps against SQL Injection &... Andrew Grosset
- Re: Securing CF Apps against SQL Injection &... Thomas Chiverton
- Re: Securing CF Apps against SQL Injecti... Andrew Grosset
- Re: Securing CF Apps against SQL In... Andrew Grosset
- Re: Securing CF Apps against SQL In... Matt Robertson
- Re: Securing CF Apps against SQ... Andrew Grosset
- Re: Securing CF Apps agains... Thomas Chiverton
- Re: Securing CF Apps against SQL Injection &... Jim Louis