Kingdom: Environment
This section includes everything that is outside of the source code but is still critical to the security of the product that is being created. Because the issues covered by this kingdom are not directly related to source code, we separated it from the rest of the kingdoms.
Web Server Misconfiguration: Response Headers
Abstract
Each browser responds differently to an incorrectly formatted response header, which can pose security implications.
Explanation
Incorrectly formatted headers can result in an inconsistent security policy and user experience. This can enable attackers to perform client-side attacks even on applications that implement declarative security directives. For example, a missing space between ":" a header name and the header value might result in some browsers ignoring the header.
References
[1] RFC 2616 - HyperText Transfer Protocol 1.1 Internet Engineering Task Force (ietf)
[2] RFC 7231 - Hypertext Transfer Protocol: Semantics and Content Internet Engineering Task Force (ietf)
[3] Standards Mapping - Common Weakness Enumeration CWE ID 436
[4] Standards Mapping - FIPS200 CM
[5] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data
[6] Standards Mapping - NIST Special Publication 800-53 Revision 4 CM-6 Configuration Settings (P1)
[7] Standards Mapping - NIST Special Publication 800-53 Revision 5 CM-6 Configuration Settings
[8] Standards Mapping - OWASP API 2023 API8 Security Misconfiguration
[9] Standards Mapping - OWASP Application Security Verification Standard 4.0 13.2.5 RESTful Web Service Verification Requirements (L2 L3)
[10] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls
[11] Standards Mapping - OWASP Top 10 2004 A10 Insecure Configuration Management
[12] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration
[13] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration
[14] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration
[15] Standards Mapping - OWASP Top 10 2021 A05 Security Misconfiguration
[16] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.10
[17] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective C.3.1 - Web Software Attack Mitigation
[18] Standards Mapping - Web Application Security Consortium Version 2.00 Server Misconfiguration (WASC-14)
desc.dynamic.xtended_preview.web_server_misconfiguration_response_headers