Kingdom: Encapsulation

Encapsulation is about drawing strong boundaries. In a web browser that might mean ensuring that your mobile code cannot be abused by other mobile code. On the server it might mean differentiation between validated data and unvalidated data, between one user's data and another's, or between data users are allowed to see and data that they are not.

Python Bad Practices: Leftover Debug Code

Python

Abstract

Debug code can create unintended entry points in a deployed web application.

Explanation

It is common practice to output the values of variables for debugging or testing purposes with code that is not intended to be shipped or remain active in the deployed application. When this sort of debug code is accidentally left in the application, the application might provide information to an attacker in unintended ways. Not all debug statements leak sensitive or private information. However, the presence of a debug statement often indicates that the surrounding code has been neglected and might be in a state of disrepair.

References

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

[2] Standards Mapping - CIS Amazon Elastic Kubernetes Service Benchmark 4

[3] Standards Mapping - CIS Amazon Web Services Foundations Benchmark 1

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

[5] Standards Mapping - Common Weakness Enumeration CWE ID 489

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

[7] Standards Mapping - OWASP Top 10 2007 A6 Information Leakage and Improper Error Handling

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

[9] Standards Mapping - OWASP Application Security Verification Standard 4.0 14.3.2 Unintended Security Disclosure Requirements (L1 L2 L3), 14.2.2 Dependency (L1 L2 L3)

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

[11] Standards Mapping - Payment Card Industry Data Security Standard Version 1.2 Requirement 6.5.6

[12] Standards Mapping - Payment Card Industry Data Security Standard Version 2.0 Requirement 6.5.5

[13] Standards Mapping - Payment Card Industry Data Security Standard Version 3.0 Requirement 6.5.5

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

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

[16] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.5

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

[18] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 3.6 - Sensitive Data Retention

[19] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 3.6 - Sensitive Data Retention

[20] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 3.6 - Sensitive Data Retention

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

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

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

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

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

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

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

desc.semantic.python.python_bad_practices_leftover_debug_code