J2EE Misconfiguration: Weak Access Permissions

ABSTRACT

不要將調用 EJB 方法的權限授予 ANYONE 這一角色。

EXPLANATION

如果 EJB 部署描述符包含一個或多個方法，并且這些方法被授予了特殊的 ANYONE 角色的訪問權限，這表明編程人員沒有全面考慮應用程序的 access control，或者應用程序的構造方式決定了不可能進行合理的 access control 限制。

例 1：以下部署描述符授權給了 ANYONE，允許其調用 Employee EJB 的 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>

REFERENCES

[1] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A10 Failure to Restrict URL Access

[2] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A2 Broken Access Control

[3] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A8 Failure to Restrict URL Access

[4] Standards Mapping - FIPS200 - (FISMA) AC

[5] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3480.2 CAT II

[6] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3480.2 CAT II

[7] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 9

[8] Standards Mapping - Web Application Security Consortium 24 + 2 - (WASC 24 + 2) Insufficient Authentication

[9] A. Taylor et al. J2EE & Java:Developing Secure Web Applications with Java Technology (Hacking Exposed) Osborne/McGraw-Hill

[10] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 6.5.10, Requirement 7.2

[11] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.2, Requirement 7.2

[12] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 6.5.8, Requirement 7.2

97av