Security issue - EL injection via DynamicContentStreamer

Components, Ajax Framework, Utilities and More.
User avatar
optimus.prime
Prime
Posts: 17394
Joined: 05 Jan 2009, 00:21
Location: Cybertron
Contact:

23 May 2011, 23:14

There are plans to drop dynamiccontentstreamer and use our custom ResourceHandler to do this stuff for 3.0.


robert.m
Posts: 226
Joined: 07 Dec 2010, 22:52
Location: Salzburg/Austria

24 May 2011, 01:45

Ok now I was able to reproduce this. I was using Tomcat 7.0.4. Thanks for posting your filter, I'll include this in my project!

pavel.horal
Posts: 11
Joined: 27 Apr 2011, 18:00

24 May 2011, 10:26

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
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.

aliok_tr
Posts: 2
Joined: 19 Mar 2011, 02:08

30 May 2011, 16:16

The following code could be used to prevent the injection until this issue is resolved:
Yes, simple solution.

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...

Cheers,

pavel.horal
Posts: 11
Joined: 27 Apr 2011, 18:00

30 May 2011, 17:18

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.
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.

Post Reply
  • Information
  • Who is online

    Users browsing this forum: Google [Bot] and 16 guests