|
|
J2EE Misconfiguration: Weak Access Permissions for EJB Methods Status: Draft Weakness ID: 9 (Weakness Variant)Description Summary If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the software system. Potential Mitigations Follow the principle of least privilege when assigning access rights to EJB methods. Permission to invoke EJB methods should not be granted to the ANYONE role. Demonstrative Examples The following deployment descriptor grants ANYONE permission to invoke the Employee EJB's method named getSalary(). <ejb-jar> ... <assembly-descriptor> <method-permission> <role-name>ANYONE</role-name> <method> <ejb-name>Employee</ejb-name> <method-name>getSalary</method-name> </method-permission> </assembly-descriptor> ... </ejb-jar>
Other Notes If the EJB deployment descriptor contains one or more method permissions that grant access to the special ANYONE role, it indicates that access control for the application has not been fully thought through or that the application is structured in such a way that reasonable access control restrictions are impossible. Relationships
Taxonomy Mappings
Time of Introduction  Architecture and Design ImplementationContent History Submissions 7 Pernicious Kingdoms. (Externally Mined) Modifications Eric Dalci. Cigital. 2008-07-01. (External) updated Time_of_Introduction CWE Content Team. MITRE. 2008-09-08. (Internal) updated Relationships, Other_Notes, Taxonomy_Mappings Previous Entry Names J2EE Misconfiguration: Weak Access Permissions (changed 2008-04-11) |
|
|
|||
