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.

Insecure Deployment: Path Normalization Conflict

Universal

Abstract

Path Normalization Conflict can allow attackers to gain access to sensitive resources that would otherwise be inaccessible.

Explanation

Path Normalization Conflict can occur in systems with multi-layered architecture where the components have different approaches to Path Normalization process. An attacker can bypass allow list and deny list ACL rules on intermediate components and as a result sensitive resources are unexpectedly exposed.
Example:
Using the proxy_pass directive, NGINX can forward all requests for /publicfolder to the Tomcat server. The developer expects that only this folder is accessible to users. However, an attacker can send the next request http://targetserver/publicfolder/..;/manager/html
NGINX considers ..; to be a folder name so the path matches the rule and this request is forwarded to the Tomcat server.
The Tomcat server considers ..; to indicate parent directory and will map the request to /publicfolder/../manager/html, giving the attacker access to the manager app of Tomcat server.

References

[1] Orange Tsai Breaking Parser Logic

[2] Standards Mapping - CIS Azure Kubernetes Service Benchmark 2

[3] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 3

[4] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 4

[5] Standards Mapping - CIS Google Kubernetes Engine Benchmark normal

[6] Standards Mapping - DISA Control Correlation Identifier Version 2 CCI-002754

[7] Standards Mapping - FIPS200 CM

[8] Standards Mapping - General Data Protection Regulation (GDPR) Indirect Access to Sensitive Data

[9] Standards Mapping - NIST Special Publication 800-53 Revision 4 SI-10 Information Input Validation (P1)

[10] Standards Mapping - NIST Special Publication 800-53 Revision 5 SI-10 Information Input Validation

[11] Standards Mapping - OWASP Top 10 2004 A10 Insecure Configuration Management

[12] Standards Mapping - OWASP Top 10 2007 A10 Failure to Restrict URL Access

[13] Standards Mapping - OWASP Top 10 2010 A6 Security Misconfiguration

[14] Standards Mapping - OWASP Top 10 2013 A6 Sensitive Data Exposure

[15] Standards Mapping - OWASP Top 10 2017 A6 Security Misconfiguration

[16] Standards Mapping - OWASP Top 10 2021 A05 Security Misconfiguration

[17] Standards Mapping - OWASP API 2023 API8 Security Misconfiguration

[18] Standards Mapping - OWASP Mobile 2014 M1 Weak Server Side Controls

[19] Standards Mapping - OWASP Mobile 2024 M2 Inadequate Supply Chain Security

[20] Standards Mapping - Payment Card Industry Data Security Standard Version 1.1 Requirement 6.5.10

[21] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.5.10

[22] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.8

[23] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.8

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.8

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.8

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.8

[27] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0 Requirement 6.2.4

[28] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 5.4 - Authentication and Access Control

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 5.4 - Authentication and Access Control

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 5.4 - Authentication and Access Control, Control Objective C.2.3 - Web Software Access Controls

[31] Standards Mapping - Security Technical Implementation Guide Version 3.1 APP3620 CAT II

[32] Standards Mapping - Security Technical Implementation Guide Version 3.4 APP3620 CAT II

[33] Standards Mapping - Security Technical Implementation Guide Version 3.5 APP3620 CAT II

[34] Standards Mapping - Security Technical Implementation Guide Version 3.6 APP3620 CAT II

[35] Standards Mapping - Security Technical Implementation Guide Version 3.7 APP3620 CAT II

[36] Standards Mapping - Security Technical Implementation Guide Version 3.9 APP3620 CAT II

[37] Standards Mapping - Security Technical Implementation Guide Version 3.10 APP3620 CAT II

[38] Standards Mapping - Security Technical Implementation Guide Version 4.1 APSC-DV-002560 CAT I

[39] Standards Mapping - Security Technical Implementation Guide Version 4.2 APSC-DV-002560 CAT I

[40] Standards Mapping - Security Technical Implementation Guide Version 4.3 APSC-DV-002560 CAT I

[41] Standards Mapping - Security Technical Implementation Guide Version 4.4 APSC-DV-002560 CAT I

[42] Standards Mapping - Security Technical Implementation Guide Version 4.5 APSC-DV-002560 CAT I

[43] Standards Mapping - Security Technical Implementation Guide Version 4.6 APSC-DV-002560 CAT I

[44] Standards Mapping - Security Technical Implementation Guide Version 4.7 APSC-DV-002560 CAT I

[45] Standards Mapping - Security Technical Implementation Guide Version 4.8 APSC-DV-002560 CAT I

[46] Standards Mapping - Security Technical Implementation Guide Version 4.9 APSC-DV-002560 CAT I

[47] Standards Mapping - Security Technical Implementation Guide Version 4.10 APSC-DV-002560 CAT I

[48] Standards Mapping - Security Technical Implementation Guide Version 4.11 APSC-DV-002560 CAT I

[49] Standards Mapping - Security Technical Implementation Guide Version 5.1 APSC-DV-002560 CAT I

[50] Standards Mapping - Security Technical Implementation Guide Version 5.2 APSC-DV-002560 CAT I

[51] Standards Mapping - Security Technical Implementation Guide Version 5.3 APSC-DV-002560 CAT I

[52] Standards Mapping - Web Application Security Consortium Version 2.00 Information Leakage (WASC-13)

[53] Standards Mapping - Web Application Security Consortium 24 + 2 Information Leakage

desc.dynamic.xtended_preview.insecure_deployment_path_normalization_conflict