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: Open Proxy Access

Universal

Abstract

A proxy server allowing CONNECT or GET requests without any restriction can enable an attacker to masquerade the origin of their attacks or access resources internal to the network.

Explanation

Some proxy servers accept the CONNECT or GET method to make an HTTP connection to another server. Usually, this method is restricted to internal use only. If it is not restricted, attackers can use the server can to disguise the origin of their attacks. Attackers might also be able to access internal machines through the proxy server and map the internal network. This type of vulnerability is usually caused by not properly configuring the proxy server.

References

[1] Standards Mapping - Common Weakness Enumeration CWE ID 441

[2] Standards Mapping - FIPS200 CM

[3] Standards Mapping - General Data Protection Regulation (GDPR) Access Violation

[4] Standards Mapping - NIST Special Publication 800-53 Revision 4 CA-3 System Interconnections (P1)

[5] Standards Mapping - NIST Special Publication 800-53 Revision 5 CA-3 Information Exchange

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

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

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

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

[10] Standards Mapping - OWASP Top 10 2013 A10 Unvalidated Redirects and Forwards

[11] Standards Mapping - OWASP Top 10 2021 A01 Broken Access Control

[12] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.4

[13] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.4

[14] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.4

[15] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.4

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

[17] Standards Mapping - Payment Card Industry Data Security Standard Version 4.0.1 Requirement 6.2.4

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

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

[20] 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

[21] Standards Mapping - Web Application Security Consortium Version 2.00 Server Misconfiguration (WASC-14)

desc.dynamic.xtended_preview.web_server_misconfiguration_open_proxy_access