Secret in Build Argument

critical

Detects ARG instructions with names suggesting secrets. Build args are visible in image history

Rule Information

Language
Docker
Category
Container Security
Author
Code Pathfinder Team
Last Updated
2024-12-10
Tags
dockersecretscredentialsleak
CWE References
CWE-538

Interactive Playground

Experiment with the vulnerable code and security rule below. Edit the code to see how the rule detects different vulnerability patterns.

pathfinder scan --rule cpf/docker-secret-arg
Vulnerable Code
Security Rule

Similar Rules

Explore related security rules for Docker

high

Container Running as Root

Detects Dockerfiles without USER instruction, causing containers to run with root privileges

critical

Docker Socket Mounted as Volume

Detects Docker socket mount which gives container full control over host Docker daemon

medium

Base Image Uses :latest Tag

Detects FROM instructions using :latest tag which makes builds non-reproducible

Frequently Asked Questions

Common questions about Secret in Build Argument

Detects ARG instructions with names suggesting secrets. Build args are visible in image history
This vulnerability is rated as critical severity, which means it requires immediate attention and can lead to severe security breaches such as remote code execution, complete system compromise, or massive data breaches.

Use Code Pathfinder to scan your Docker codebase and automatically detect instances of this vulnerability pattern. Install Code Pathfinder and run the following command in your project directory:

pathfinder scan --rule cpf/docker-secret-arg

This rule is aligned with industry-standard security frameworks and classifications:

  • CWE (Common Weakness Enumeration): CWE-538
  • Tags: docker, secrets, credentials, leak
Yes! Code Pathfinder allows you to customize rules to match your specific security requirements and coding standards. You can modify the detection patterns, adjust severity levels, add custom sanitizers, and configure the rule to fit your organization's security policies. The interactive playground above lets you experiment with the rule and see how it behaves with different code patterns.
When this vulnerability is detected in your code, review the flagged instances carefully. Check the "Vulnerable Code" section above for examples of insecure patterns and the "Security Rule" section to understand what the rule is looking for. Follow security best practices for Docker and consult the CWE/CVE references for detailed remediation guidance. Always test your fixes thoroughly before deploying to production.
Back to Container SecurityAll Languages →
Secret in Build Argument - Docker Security Rule | Code Pathfinder | Code Pathfinder