Bug 44445
| Summary: | Reflective XSS Protection and ASP unicode messing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Giovanni Bajo <rasky> |
| Component: | WebCore Misc. | Assignee: | Nobody <webkit-unassigned> |
| Status: | UNCONFIRMED | ||
| Severity: | Normal | CC: | abarth, rasky |
| Priority: | P2 | ||
| Version: | 528+ (Nightly build) | ||
| Hardware: | PC | ||
| OS: | OS X 10.5 | ||
Giovanni Bajo
The Reflective XSS Protection currently present in Chrome/Webkit fails to handle a weird unicode "pruning" made by ASP servers (where they substitute omoglyphs). The issue is well detailed in this blog post:
http://hackademix.net/2010/08/17/lost-in-translation-asps-homoxssuality/
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Adam Barth
We could normalize these before comparison, but there's a long tail of complex transformations like this. It's unclear whether we're better off chasing that tail or letting these folks realize that magically substituting one character for another is a bad idea.