rules-chef

Potential command injection vulnerability detected in 'execute' resource. Using unsanitized node attributes directly in shell commands can lead to arbitrary code execution. Sanitize all external inputs using shell_escape or prefer Chef's built-in resources over raw 'execute' for common tasks.

Deprecated use of 'node.set' in recipes. 'node.set' overrides all other attribute precedence levels and can lead to unexpected behavior or security issues if used improperly. Prefer 'node.default' for setting defaults or 'node.override' with caution for explicit overrides.

Chef style guide violation (Foodcritic FC019). Access node attributes using `node['attribute']` not `node.attribute` for consistency and to avoid potential method conflicts. Consider running Foodcritic for full style and best practice checks.

Hardcoded sensitive data (e.g., passwords, API keys) detected. This is a critical security vulnerability. Use Chef Vault or encrypted data bags for secret management. Never store secrets directly in recipes or attributes.

Insecure file/directory permissions. Resources like 'file', 'directory', or 'template' should explicitly define a secure 'mode' (e.g., '0644' for files, '0755' for directories) to prevent unintended access. Omitting 'mode' can result in overly permissive defaults.

Insecure HTTP request with SSL verification disabled. Using 'verify_ssl :verify_none' exposes your system to Man-in-the-Middle attacks. Always ensure SSL verification is enabled for production environments.

Remote file download without checksum verification. Downloading files without a 'checksum' attribute makes your system vulnerable to Man-in-the-Middle attacks or corrupted files. Always specify a strong checksum (e.g., SHA256) for remote files.