Closed (fixed)
Project:
Vulnerability Blocker
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
4 Aug 2011 at 15:40 UTC
Updated:
18 Aug 2011 at 20:41 UTC
I tried creating a node with XSS in the title, body, and a cck text field. These were all accepted and since I had a purposely vulnerable module on my site were printed back to me.
Does this module prevent persistent XSS or reflected? both? neither?
Comments
Comment #1
gregglesUpdated title since I tried a few more things after writing it.
Comment #2
dave reidI don't see how this actually prevents any XSS at all.
Comment #3
dave reidComment #4
sudeepg commentedHi David,
Thanks for testing the module.
Lot of XSS attacks happen due to script tags being put up in the URL and to execute them hackers use '<', '>' to enclose tags. We did some extensive testing on few of our production sites using some renowned XSS scanners and it was difficult to plug them all. This simple fix plugged all attacks and it has been months we have seen any XSS alert on any of them.
I hope this information helps.
Thanks,
Sudeep
Comment #5
sudeepg commentedThis module is not a replacement for check_plain which is intended to be used wherever possible in open drupal forms, but a generic url filter to avoid hackers from exploiting URLs. So, we are trying to sanitize cross-site suspicious GET requests here.
Comment #6
gregglesSo it's for reflected XSS. It would be great if you could state that more clearly on the project page.
Comment #7
sudeepg commentedI will do that. Thanks for providing feedback. I mark this item closed now.
Comment #8
tim.plunkettSet to "fixed", not "closed (fixed)". http://drupal.org/node/156119#closed