RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 927934 - java.security.AccessControlException: access denied on tomcat6 rpm running with security manager
Summary: java.security.AccessControlException: access denied on tomcat6 rpm running wi...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: tomcat6
Version: 6.4
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: David Knox
QA Contact: tomcat-qe
URL:
Whiteboard:
Depends On: 927930
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-26 14:25 UTC by Michal Haško
Modified: 2015-11-02 00:18 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 927930
Environment:
Last Closed: 2014-01-20 21:17:02 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michal Haško 2013-03-26 14:25:45 UTC 
+++ This bug was initially created as a clone of Bug #927930 +++

Created attachment 716541 [details]
reproducer app

Description of problem:
This issue was discovered while testing if security manager works properly on tomcat6 rpm. The test itself was denied runtime permissions.

Version-Release number of selected component (if applicable):
tomcat6-6.0.24-52.el6_4.noarch

How reproducible:
100%

Steps to Reproduce:
1. enable security manager (SECURITY_MANAGER=true in /etc/tomcat6/tomcat6.conf)
1. deploy app smtest (in attachment)
2. start tomcat # service tomcat6 start
3. visit http://$(hostname):8080/smtest/test.jsp
  
Actual results:
java.security.AccessControlException: access denied ("java.lang.RuntimePermission" "accessClassInPackage.org.apache.jasper")
	java.security.AccessControlContext.checkPermission(AccessControlContext.java:366)
	java.security.AccessController.checkPermission(AccessController.java:560)
	java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
	java.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1529)
	sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:305)
	java.lang.ClassLoader.loadClass(ClassLoader.java:410)
	java.lang.ClassLoader.loadClass(ClassLoader.java:356)
	org.apache.jasper.servlet.JspServletWrapper.<init>(JspServletWrapper.java:98)
	org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:305)
	org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
	javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
	sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	java.lang.reflect.Method.invoke(Method.java:601)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:270)
	org.apache.catalina.security.SecurityUtil$1.run(SecurityUtil.java:268)
	java.security.AccessController.doPrivileged(Native Method)
	javax.security.auth.Subject.doAsPrivileged(Subject.java:536)
	org.apache.catalina.security.SecurityUtil.execute(SecurityUtil.java:302)
	org.apache.catalina.security.SecurityUtil.doAsPrivilege(SecurityUtil.java:163)

Expected results:
Security Manager Test Result = pass
If you can see this text. Your security manager setup works fine.
This, of course, doesn't mean you are safe for all kinds of misbehavior.
Comment 3 RHEL Program Management 2014-01-20 21:17:02 UTC 
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
Note You need to log in before you can comment on or make changes to this bug.