T03 · Remote Payload Retrieval and Execution
- Location
install/commands.md:17- Finding
Unverified Remote Bootstrap Script Executed with Root Privileges
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This Dokku administration skill is coherent, but it needs Review because it documents root-level installs, broad SSH access grants, secret-revealing config commands, and destructive host-wide operations without enough scoping or safety guidance.
Install only if you want an agent to help administer a Dokku host. Before running commands from this skill, confirm the target host and app, avoid generic activation for non-Dokku deploys, verify downloaded installers and plugin repositories, pin trusted plugin commits where possible, add only specific reviewed public SSH keys, treat config output as secret material, and require explicit confirmation before destroy, prune, force, global-domain, certificate-removal, or bind-all-interfaces actions.
install/commands.md:17Unverified Remote Bootstrap Script Executed with Root Privileges
install/commands.md:28All Existing Authorized SSH Keys Are Granted Dokku Access
plugin/commands.md:13Unpinned Third-Party Plugins Are Installed with Root Privileges
config/commands.md:5Application Secrets Can Be Exposed Through Configuration Display and Export Commands
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
cat ~/.ssh/authorized_keys | sudo dokku ssh-keys:add admin
Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.
cat ~/.ssh/authorized_keys | sudo dokku ssh-keys:add admin
The markdown advertises capabilities such as deploying apps, cleaning up containers, and destroying apps, all of which can affect availability or permanently remove resources. The description does not include any cautionary note about data loss, downtime, or the need to verify targets before running such commands.
The trigger terms include very broad words like "deploy" and "cleanup," which are common across many unrelated tasks and can cause this skill to activate when the user did not specifically intend Dokku operations. Because this skill includes destructive and privileged actions on a Dokku host, accidental activation increases the risk of unintended deployments, pruning, or app/container modifications.
The skill advertises destructive capabilities such as app destruction, pruning, uninstall, and cleanup workflows without clear warnings, guardrails, or confirmation requirements. In a host-level administration context, users may not appreciate that these commands can permanently delete apps, containers, configuration, or runtime state, making accidental misuse materially more dangerous.
This markdown file documents dokku --force apps:destroy <app>, which permanently destroys an app and all add-ons without confirmation. Although L21 notes permanence and the normal prompt behavior, it does not explicitly warn users about the elevated risk of bypassing confirmation with --force or advise caution before using it.
This markdown file describes certs:remove as simply removing a certificate for an app, but it does not warn that doing so can disrupt TLS/HTTPS for that app or affect live traffic. For markdown files, safety-impacting actions that can affect system integrity or service availability should include a user-facing warning.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
sudo docker system prune
sudo docker system prune -f # skip confirmation
Installing a community plugin directly from a Git repository as root introduces a real supply-chain risk, because the plugin code will be fetched and installed with elevated privileges on the host. Even though the text labels it as aggressive and destructive, it does not advise pinning to a trusted commit, verifying publisher integrity, or reviewing plugin code before installation.
For aggressive cleanup (e.g. wipe everything): the community plugin dokku-nuke stops all running containers and deletes all containers and images. Use only when you intend to remove all apps and images from the host.
sudo dokku plugin:install https://github.com/dokku-community/dokku-nuke.git
# Then run per plugin docs (destructive).
The config and config:get commands display environment variables directly, but the documentation omits any caution that these values may contain credentials or other secrets. Users may run them in shared terminals, record them in shell history, or capture them in support logs and screenshots, leading to accidental exposure.
The documentation advertises config:export as useful for backups or CI but does not warn that exported application configuration commonly includes secrets such as API keys, database passwords, and tokens. In practice, users may redirect this output into logs, CI artifacts, shell history, or shared files, causing unintended secret disclosure.
This markdown file describes operations that replace or delete existing domain configuration, including domains:set, domains:clear, and domains:reset, but it does not warn users that these actions can remove current mappings and affect app routing. For markdown files, omissions of warnings about behaviors that can affect system integrity or service availability should be flagged.
The documentation includes domains:set-global, domains:remove-global, and domains:clear-global, which alter or remove global domain configuration for all apps, yet there is no warning about the broad operational impact. In markdown skill descriptions, system-wide changes that can affect user services should include clear user-facing cautions.
The instructions download a remote bootstrap script and execute it with sudo, giving network-fetched code full root privileges. Even if this is a common installation pattern, it is risky because compromise of the download source, transport, or referenced version could lead to complete host takeover.
This command runs the bootstrap installer under sudo, so any action performed by the script executes with elevated privileges. In installation documentation this may be operationally necessary, but it still creates real risk if the script is tampered with or behaves unexpectedly.
wget -NP . https://dokku.com/install/v0.37.5/bootstrap.sh
sudo DOKKU_TAG=v0.37.5 bash bootstrap.sh
Installation takes about 5–10 minutes. Then configure SSH and domain.
The documentation explicitly recommends or describes binding an app to all interfaces (0.0.0.0) without any warning that this can expose the service beyond localhost or expected internal networks. In an operations skill, users may copy commands directly, so omitting the security caveat increases the chance of accidental public exposure of admin or internal services.
This markdown file documents commands that install software from a URL and requires sudo, which can modify system state and affect system integrity. While the commands are described functionally, the file does not include an explicit warning about the risks of installing untrusted plugins or making privileged changes.
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
Download and install a plugin. Usually requires root/sudo.
sudo dokku plugin:install <url>
# Example:
sudo dokku plugin:install https://github.com/dokku/dokku-postgres.git
No suspicious patterns detected.