-
Notifications
You must be signed in to change notification settings - Fork 38.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spring Expression Language creates systemProperties bean calling System.getProperties() which in enterprise shared containers is locked down [SPR-6308] #10974
Comments
Arjen Poutsma commented Fixed. When access to System.getProperties() is denied, we now lazily access system properties via System.getProperty(String). If that is denied too, we log a warning. |
Matt Goldspink commented This looks great. Thanks Arjen. |
Sree Vaddi commented Hi, http://jira.springframework.org/browse/SPR-6287 As suggested by Matt in http://jira.springframework.org/browse/SPR-6308 The only way, I could get rid of the exception is, Now, my app loads smoothly without any exceptions. By the way, when is 3.0 RC2 release due ? Thank you very much. With Regards |
Gagandeep Singh commented I am acing this issue in Was 7 and Spring 3.1.3 Release . I added the following two properties [3/7/13 17:20:29:365 EST] 0000000b webapp I com.ibm.ws.webcontainer.webapp.WebApp log SRVE0292I: Servlet Message - [bst-51881#bst.war]:.Initializing Spring FrameworkServlet 'appServlet' Permission:
Code:
Stack Trace: java.security.AccessControlException: Access denied (java.lang.RuntimePermission getenv.*) |
Juergen Hoeller commented I suppose this is just a warning, not a fatal exception? I suppose it is logging any attempt to call System.getEnv there, even when guarded by a catch clause... Juergen |
Juergen Hoeller commented Haven't noticed before: Let's continue the discussion at #15921, the follow-up to this one... Juergen |
Matt Goldspink opened SPR-6308 and commented
We have a shared hosting environment for all our Tomcat containers in the firm and multiple teams may have webapps in the same Tomcat instance. As such the security policy is setup to disallow access to System.getProperties() as this will return a mutable view of all the system properties and if one application were to manipulate these it may adversely affect other applications in the same container.
We know the workaround for now is to simply drop in a bean named systemProperties but we would prefer a fix on the Spring side for this because it will likely catch all other groups that run a similar model to us. It seams like adding a simple bean which just delegates the call to System.getProperty("name") (which is not locked down) would be good enough to do this.
Affects: 3.0 RC1
Issue Links:
Referenced from: commits 68f57aa
The text was updated successfully, but these errors were encountered: