ABSTRACT

Not explicitly setting the <authorization> tag can result in privilege escalation or anonymous access.

EXPLANATION

The <authorization> element specifies a list of authorization rules. If an <authorization> element exists and no rules apply to a sender, access is denied [1].
In this case, no <authorization> tag exists in and anonymous access might be possible.

REFERENCES

[1] Element Microsoft

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

[3] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A10 Insecure Configuration Management

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

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

[6] Standards Mapping - FIPS200 - (FISMA) CM

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

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

[9] Standards Mapping - SANS Top 25 2009 - (SANS 2009) Porous Defenses - CWE ID 285

[10] Standards Mapping - SANS Top 25 2010 - (SANS 2010) Porous Defenses - CWE ID 285

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

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

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