ABSTRACT

A security constraint that references a non-existent role-name prevents legitimate access to all resources it protects.

EXPLANATION

A missing security-role for a role-name defined in an auth-constraint could indicate an out-of-date configuration.



Example 1: The following example specifies a role-name, but does not define it in a security-role.


<security-constraint>
<web-resource-collection>
<web-resource-name>AdminPage</web-resource-name>
<description>Admin only pages</description>
<url-pattern>/auth/noaccess/*</url-pattern>
</web-resource-collection>

<auth-constraint>
<description>Administrators only</description>
<role-name>admin</role-name>
</auth-constraint>

<user-data-constraint>
<transport-guarantee>INTEGRAL</transport-guarantee>
</user-data-constraint>
</security-constraint>

REFERENCES

[1] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A6 Security Misconfiguration

[2] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A9 Application Denial of Service

[3] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP6080 CAT II

[4] Standards Mapping - Common Weakness Enumeration - (CWE) CWE ID 730

[5] Sun Microsystems, Inc. Java Servlet Specification 2.4

[6] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.9