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.

Dockerfile Misconfiguration: Sensitive Host Directory

Docker

Abstract

Revealing sensitive host directories might give an attacker access to vital system information

Explanation

You can reconstruct a Dockerfile from a publicly available docker image using docker inspect and the history command, or by automating this process through a third-party tool. If sensitive information is added using the ADD/COPY command, an attacker can recreate each docker layer to obtain the information.

Using Volumes also can expose sensitive directories. If you need to use Volumes to persist data, avoid mounting sensitive directories.

References

[1] Docker ADD/COPY instruction

[2] Docker Volume instruction

[3] Protecting Sensitive Information

[4] Standards Mapping - Common Weakness Enumeration CWE ID 20

[5] Standards Mapping - Common Weakness Enumeration Top 25 2019 [3] CWE ID 020

[6] Standards Mapping - Common Weakness Enumeration Top 25 2020 [3] CWE ID 020

[7] Standards Mapping - Common Weakness Enumeration Top 25 2021 [4] CWE ID 020

[8] Standards Mapping - Common Weakness Enumeration Top 25 2022 [4] CWE ID 020

[9] Standards Mapping - Common Weakness Enumeration Top 25 2023 [6] CWE ID 020

[10] Standards Mapping - Common Weakness Enumeration Top 25 2024 [12] CWE ID 020

[11] Standards Mapping - FIPS200 CM

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

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

[14] Standards Mapping - OWASP Application Security Verification Standard 4.0 5.1.3 Input Validation Requirements (L1 L2 L3), 5.1.4 Input Validation Requirements (L1 L2 L3)

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

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

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

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

[19] Standards Mapping - OWASP Top 10 2013 A5 Security Misconfiguration

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

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

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

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

[24] Standards Mapping - Payment Card Industry Data Security Standard Version 3.1 Requirement 6.5.6

[25] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2 Requirement 6.5.6

[26] Standards Mapping - Payment Card Industry Data Security Standard Version 3.2.1 Requirement 6.5.6

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

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

[29] Standards Mapping - Payment Card Industry Software Security Framework 1.0 Control Objective 4.2 - Critical Asset Protection

[30] Standards Mapping - Payment Card Industry Software Security Framework 1.1 Control Objective 4.2 - Critical Asset Protection

[31] Standards Mapping - Payment Card Industry Software Security Framework 1.2 Control Objective 4.2 - Critical Asset Protection

[32] Standards Mapping - SANS Top 25 2009 Insecure Interaction - CWE ID 020

[33] Standards Mapping - Web Application Security Consortium Version 2.00 Application Misconfiguration (WASC-15)

desc.configuration.docker.dockerfile_misconfiguration_sensitive_host_directory