將應用程序配置為使 WebSphere 能夠按照 Servlet 的類名為其提供服務。
允許按照 Servlet 的類名為其提供服務會使知道 Servlet 名稱的任何攻擊者能夠直接調用它,即使沒有在應用程序的部署描述符中映射它也是如此。
例如,考慮包含名為 com.ibm.websphere.samples.MyServlet 的 Servlet 的應用程序。在 ibm-web-ext.xmi 中將 serveServletsByClassnameEnabled 設置為 true 時,可能通過以下請求調用該 servlet:http://www.example.com/SomeContextPath/servlet/com.ibm.websphere.samples.MyServlet。
更糟糕的是,根據服務器的 classloader 結構,攻擊者可能從駐留在相同 WebSphere 實例中的其他應用程序調用 Servlet。
[1] Standards Mapping - OWASP Top 10 2007 - (OWASP 2007) A10 Failure to Restrict URL Access
[2] Standards Mapping - OWASP Top 10 2004 - (OWASP 2004) A10 Insecure Configuration Management
[3] Standards Mapping - OWASP Top 10 2010 - (OWASP 2010) A6 Security Misconfiguration
[4] Standards Mapping - Security Technical Implementation Guide Version 3 - (STIG 3) APP3480.2 CAT II
[5] Standards Mapping - Security Technical Implementation Guide Version 3.4 - (STIG 3.4) APP3480.2 CAT II
[6] Standards Mapping - FIPS200 - (FISMA) CM
[7] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 - (PCI 1.1) Requirement 6.5.10, Requirement 7.2
[8] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 - (PCI 1.2) Requirement 6.5.10, Requirement 7.2
[9] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 - (PCI 2.0) Requirement 6.5.8, Requirement 7.2
[10] Keys Botzum WebSphere Application Server V6 advanced security hardening -- Part 1