Most static code-execution alerts were markdown code fence false positives, not Ruby backtick execution. Confirmed issues remain around cluster-changing setup commands, direct remote manifest application, and a Flux install command that pipes network content to sudo bash. No prompt injection text was found.
This fenced bash block creates namespaces, applies a remote manifest, and reads the initial admin secret. It is legitimate setup guidance but can mutate clusters and expose sensitive credentials if run automatically.
The troubleshooting block includes argocd app sync with prune, which can change or delete cluster resources. It should require explicit cluster and environment confirmation.
The high-availability install also applies a remote GitHub manifest directly to the cluster. This is legitimate setup guidance but carries supply-chain risk.
The setup example applies a Kubernetes manifest from a remote GitHub URL. This is common but should be reviewed and pinned before cluster installation.
The production Application example uses apps/production/my-app with automated sync, prune, and selfHeal. If copied directly, it can delete or rewrite production resources without approval.
The file warns against production auto-sync at line 38, but the later production path example enables automated prune and selfHeal. This is a clear operational safety gap.
The repo-add example places a repository token in a command-line password argument. Users could expose tokens through shell history, logs, or process listings.
The token value is a placeholder, but the documented pattern teaches command-line secret handling. No real secret is embedded.
04
是正措置
この監査で推奨される修正が記録されています。これらを適用する責任はメンテナーにあります。
FIX-001
高
Remote install script with root privileges
Replace the curl-to-sudo Flux install command with a pinned package, checksum verification, or manual review step.
FIX-002
中
Remote Kubernetes manifest application
Pin exact ArgoCD release URLs and tell users to inspect manifests before applying them to a cluster.
FIX-003
中
Production auto-sync with prune in examples
Change production examples to manual sync or approval-gated sync. Reserve automated prune and selfHeal for lower environments.
FIX-004
中
Repository token shown as a command argument
Use credential prompts, environment-specific secret stores, or documented secure token handling instead of command-line password arguments.