Re:Massive Twitter Cross-Site Scripting Vulnerability
by mrkurt on Tuesday August 25, 2009 @08:29PM
(#786229)
It's odd that you count completely on validation to catch problems like this, rather than escaping the output as well. Writing regex validations to prevent malicious input seems like a seriously error prone thing to be doing.
[ Parent
| on HN ]
Re:Massive Twitter Cross-Site Scripting Vulnerability
by qeorge on Tuesday August 25, 2009 @09:37PM
(#786327)
Agree. Not trying to give you guys a hard time, but Twitter has had several vulnerabilities caused by unescaped user supplied data being output without sanitization.
Obviously I'm on the outside looking in, but IIRC rendering user pages is not particularly taxing on Twitter, to the point that they aren't cached. Would adding a simple sanitization routine have significant impact?