This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "J2EE Misconfiguration: Weak Access Permissions"

From OWASP
Jump to: navigation, search
m (Reverted edits by SitleTorac (Talk) to last version by KirstenS)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Template:Vulnerability}}
+
{{template:CandidateForDeletion}}
{{Template:Fortify}}
+
 
 +
#REDIRECT [[Least Privilege Violation]]
  
[[Category:FIXME|This is the text from the old template. This needs to be rewritten using the new template.]]
 
  
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
Last revision (mm/dd/yy): '''{{REVISIONMONTH}}/{{REVISIONDAY}}/{{REVISIONYEAR}}'''
 
[[ASDR_TOC_Vulnerabilities|Vulnerabilities Table of Contents]]
 
 
[[ASDR Table of Contents]]
 
__TOC__
 
  
  
Line 73: Line 68:
  
  
[[Category:FIXME|add links
 
 
In addition, one should classify vulnerability based on the following subcategories: Ex:<nowiki>[[Category:Error Handling Vulnerability]]</nowiki>
 
 
Availability Vulnerability
 
 
Authorization Vulnerability
 
 
Authentication Vulnerability
 
 
Concurrency Vulnerability
 
 
Configuration Vulnerability
 
 
Cryptographic Vulnerability
 
 
Encoding Vulnerability
 
 
Error Handling Vulnerability
 
 
Input Validation Vulnerability
 
 
Logging and Auditing Vulnerability
 
 
Session Management Vulnerability]]
 
  
 
__NOTOC__
 
__NOTOC__
 
 
[[Category:OWASP ASDR Project]]
 
[[Category:Environmental Vulnerability]]
 
[[Category:Access Control Vulnerability]]
 
[[Category:Code Permission Vulnerability]]
 
[[Category:Implementation]]
 
[[Category:Deployment]]
 
[[Category:Java]]
 
[[Category:Code Snippet]]
 

Latest revision as of 19:55, 26 May 2009

Template:CandidateForDeletion

#REDIRECT Least Privilege Violation


Last revision (mm/dd/yy): 05/26/2009


Description

Permission to invoke EJB methods should not be granted to the ANYONE role.

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.


Risk Factors

  • Talk about the factors that make this vulnerability likely or unlikely to actually happen
  • Discuss the technical impact of a successful exploit of this vulnerability
  • Consider the likely [business impacts] of a successful attack


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>


Related Attacks


Related Vulnerabilities


Related Controls


Related Technical Impacts


References

TBD