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: Missing Unicode Charset
Abstract
Allowing user input to control the web page's character set can enable an attacker to bypass application's user input filters.
Explanation
Programmers can use input filters to protect applications from client-side threats such as Cross-Site Scripting. However, if the application fails to ensure strict enforcement of an appropriate character set for all the web pages, an attacker can generate payloads using a character set that differs from the one that the input filters use. Similarly, a vulnerability that enables user supplied input to modify the character set of a web page can result in a similar outcome. By changing the character set, an attacker can send malicious payloads, which are ignored by the application's input filter as the characters are deemed safe.
For instance, a UTF-7 encoded cross-site scripting payload
For instance, a UTF-7 encoded cross-site scripting payload
+ADw-script+AD4-alert(document.location)+ADw-/script+AD4 bypasses UTF-8 based input filters.References
[1] Standards Mapping - Common Weakness Enumeration CWE ID 116
[2] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-001310
[3] Standards Mapping - FIPS200 CM
[4] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data
[5] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1), SI-15 Information Output Filtering (P0)
[6] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation, SI-15 Information Output Filtering
[7] Standards Mapping - OWASP API 2023 API8 Security Misconfiguration
[8] Standards Mapping - OWASP Application Security Verification Standard 4.0 1.5.4 Input and Output Architectural Requirements (L2 L3), 5.2.1 Sanitization and Sandboxing Requirements (L1 L2 L3), 5.3.1 Output Encoding and Injection Prevention Requirements (L1 L2 L3), 13.1.1 Generic Web Service Security Verification Requirements (L1 L2 L3), 14.4.2 HTTP Security Headers Requirements (L1 L2 L3), 14.4.4 HTTP Security Headers Requirements (L1 L2 L3)
[9] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls
[10] Standards Mapping - OWASP Top 10 2004 A10 Insecure Configuration Management
[11] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration
[12] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration
[13] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration
[14] Standards Mapping - OWASP Top 10 2021 A05 Security Misconfiguration
[15] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.10
[16] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.6
[17] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.6
[18] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.6
[19] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.6
[20] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4
[21] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4
[22] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection
[23] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection
[24] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection
[25] Standards Mapping - SANS Top 25 2009 Insecure Interaction - CWE ID 116
[26] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002520 CAT II
[27] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002520 CAT II
[28] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002520 CAT II
[29] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002520 CAT II
[30] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002520 CAT II
[31] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002520 CAT II
[32] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002520 CAT II
[33] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002520 CAT II
[34] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002520 CAT II
[35] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002520 CAT II
[36] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002520 CAT II
[37] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002520 CAT II
[38] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002520 CAT II
[39] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002520 CAT II
[40] Standards Mapping - Security Technical Implementation Guide Version 6.1 APSC-DV-002520 CAT II
[41] Standards Mapping - Security Technical Implementation Guide Version 6.2 APSC-DV-002520 CAT II
[42] Standards Mapping - Web Application Security Consortium Version 2.00 Server Misconfiguration (WASC-14)
desc.dynamic.xtended_preview.web_server_misconfiguration_missing_unicode_charset