Components, Ajax Framework, Utilities and More.
Glad to hear that (I would vote to reclassify as a bug or at least assign higher priority). I am still willing to send you the exploit if you are interested.There are plans to drop dynamiccontentstreamer and use our custom ResourceHandler to do this stuff for 3.0.
http://code.google.com/p/primefaces/iss ... il?id=2073
Yes, simple solution.The following code could be used to prevent the injection until this issue is resolved:
However, if one uses JSF's error handling mechanism the way the error page is also served by JSF, then the result of the exploit still might be shown.
So, in our case, we made a redirection to a page not served by JSF.
Just a heads up...
Very good point. We use JSF error pages... however the ERROR dispatch is also caught (second time) by the protecting servlet filter. We end up with showing the error page of the servlet container.However, if one uses JSF's error handling mechanism the way the error page is also served by JSF, then the result of the exploit still might be shown.
Who is online
Users browsing this forum: Google [Bot] and 16 guests