Back to skill

Security audit

volcengine-deploy

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this deployment skill suspicious because scanners report exposed smoke-test services, unsafe packaging and secret handling, broad network access, and other deployment risks; the analysis is also incomplete.

Consider the review findings before installing, especially the reported exposure of test services, broad deployment packaging, local storage of credentials, network policy, and migration and permission changes. The scan is partial: 9 of 12 components were fully inspected and 3 were partially inspected, so the available results cannot establish that the entire skill is safe.

Vulnerability Patterns
  • Insecure Skill Coding PracticesFinds exploitable flaws such as hardcoded secrets or command injection
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
Findings (1)

T09 · Insecure Skill Coding Practices

Warning
Location
scripts/gen-docker-compose-test.sh
Finding

Local smoke-test dependencies are published beyond localhost without effective authentication

Content
View full analysis

Impact

Reachable peers can read or modify smoke-test database contents and interfere with application validation. This does not establish exposure of production data or compromise of the host.

Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Tool MisuseTool Parameter Abuse, Chaining Abuse, Unsafe Defaults
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (51)

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 238)May include surrounding context.

md
Read [`references/ecs-deploy-steps.md`](./references/ecs-deploy-steps.md) for the detailed ECS packaging, upload, Cloud Assistant, Docker mirror, architecture,

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 328)May include surrounding context.

md
- ECS build/systemd/upload details: [`references/ecs-deploy-steps.md`](./references/ecs-deploy-steps.md)

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 341)May include surrounding context.

md
- ECS instance/image/Cloud Assistant/SSH/Docker mirror issues: [`references/ecs-deploy-steps.md`](./references/ecs-deploy-steps.md)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 272)May include surrounding context.

md
Keep this ordered execution skeleton — these actions must be chained in sequence, and a later step run before an earlier one converges is the most common VKE failure:

1. Provision or reuse VKE + CR (IaC outputs or CLI fast path).
2. Wait for the cluster to be `Running`, then fetch the kubeconfig (from IaC outputs or `CreateKubeconfig`).
3. Verify addons: `core-dns` present; prefer `cr-credential-controller` for private CR pulls.
4. Build the image for the node architecture.
5. Authenticate to CR, push the image, and inspect the pushed platform.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/vke-deploy-steps.md (reported line 11)May include surrounding context.

md
### 1. Provision or reuse VKE + CR

- `infra_management=iac`: use `volcengine-iac` outputs in `.volcengine/iac-outputs.json` for VPC/subnets/security group, `cluster_id`, CR registry/namespace/repository, and (when present) `kubeconfig_private`.
- CLI fast path: create or reuse VPC/subnet/security group, the VKE cluster + node pool, and a CR registry/namespace/repository, recording every CLI-created resource in `.volcengine/created-resources.json` immediately. Reuse a user-specified cluster/registry when given.

Do not hardcode node instance types. Build the image for the node architecture (default `linux/amd64` unless node-pool data proves otherwise).

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/vke-deploy-steps.md (reported line 30)May include surrounding context.

[ "$phase" = "Running" ] || { echo "cluster not Running: $phase" >&2; exit 1; }

text

Then read kubeconfig from `.volcengine/iac-outputs.json` when present, otherwise create one:

```bash
ve vke CreateKubeconfig --ClusterId "$cluster_id" --Type Public

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 272)May include surrounding context.

md
Keep this ordered execution skeleton — these actions must be chained in sequence, and a later step run before an earlier one converges is the most common VKE failure:

1. Provision or reuse VKE + CR (IaC outputs or CLI fast path).
2. Wait for the cluster to be `Running`, then fetch the kubeconfig (from IaC outputs or `CreateKubeconfig`).
3. Verify addons: `core-dns` present; prefer `cr-credential-controller` for private CR pulls.
4. Build the image for the node architecture.
5. Authenticate to CR, push the image, and inspect the pushed platform.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/vke-deploy-steps.md (reported line 37)May include surrounding context.

Decode the returned Kubeconfig (base64) to a file and export KUBECONFIG.

text

`CreateKubeconfig` before the cluster is `Running` returns `OperationDenied` — that is why the poll above must succeed first. Use `--Type Private` only when the agent runs inside the VPC.

### 3. Verify addons

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 285)May include surrounding context.

md
Keep these hard boundaries in the main context:

- Use IaC outputs for VPC/subnets/security group/VKE/CR when available; otherwise create or reuse through the CLI fast path and record resources.
- `CreateKubeconfig` before the cluster is `Running` returns `OperationDenied` — poll to `Running` first.
- Confirm `core-dns` before relying on in-cluster DNS.
- Prefer `cr-credential-controller` for private Volcengine CR image pulls instead of storing registry passwords in app manifests.
- Re-read `Result.Username` from `GetAuthorizationToken` for `docker login`; never invent a fallback username.

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/k8s-manifests.md (reported line 353)May include surrounding context.

md
| Symptom | Cause | Fix |
|---|---|---|
| `CreateKubeconfig` returns `OperationDenied` | cluster not yet `Running` | Poll `ListClusters` until `Status.Phase=Running` before fetching the kubeconfig |
| `Service` `LoadBalancer` stuck at `<pending>` | missing CLB subnet annotation | Add `service.beta.kubernetes.io/volcengine-loadbalancer-subnet-id` to the Service |
| `BLB no available backend` / no available backend nodes | Pod readinessProbe failing, often because the probed `/health` path does not exist | Use the actual detected health path, or switch the probe to `tcpSocket`; diagnose with `kubectl describe pod` + `kubectl logs` |
| Container exits immediately with `exec format error` | image architecture does not match the VKE node architecture | Rebuild/pull/push with the node architecture (usually `linux/amd64`) and inspect the image platform before rollout (see [`dockerfile-templates.md`](./dockerfile-templates.md)) |

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 295)May include surrounding context.

md
manifests.md) for manifest templates and [`references/dockerfile-templates.md`](./references/dockerfile-templates.md) for image build templates.

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 331)May include surrounding context.

md
- Dockerfile templates: [`references/dockerfile-templates.md`](./references/dockerfile-templates.md)

Incomplete referenced artifact analysis

High
Category
analysis-evasion
Confidence
100% confidence
Finding

Referenced artifact was not completely inspected

Content

Scanner excerpt · SKILL.md (reported line 342)May include surrounding context.

md
- Container architecture and Dockerfile pitfalls: [`references/dockerfile-templates.md`](./references/dockerfile-templates.md)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 295)May include surrounding context.

md
For managed dependencies, prefer managed Volcengine services when practical; otherwise state clearly when the plan is deploying stateful containers inside VKE.

Read [`references/vke-deploy-steps.md`](./references/vke-deploy-steps.md) for the full VKE pipeline (cluster wait, kubeconfig, addon checks, CR auth/push, rollout, endpoint verify), with [`references/k8s-manifests.md`](./references/k8s-manifests.md) for manifest templates and [`references/dockerfile-templates.md`](./references/dockerfile-templates.md) for image build templates.

---

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 329)May include surrounding context.

md
- Always before provisioning: deployment plan template, gate, and resource plan in [`references/deployment-plan-template.md`](./references/deployment-plan-template.md)
- ECS build/systemd/upload details: [`references/ecs-deploy-steps.md`](./references/ecs-deploy-steps.md)
- VKE deploy pipeline (cluster/kubeconfig/addons/CR/rollout): [`references/vke-deploy-steps.md`](./references/vke-deploy-steps.md)
- veFaaS deploy handoff details: [`references/faas-deploy-steps.md`](./references/faas-deploy-steps.md)
- Dockerfile templates: [`references/dockerfile-templates.md`](./references/dockerfile-templates.md)
- Kubernetes manifests: [`references/k8s-manifests.md`](./references/k8s-manifests.md)

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · SKILL.md (reported line 343)May include surrounding context.

md
- ECS instance/image/Cloud Assistant/SSH/Docker mirror issues: [`references/ecs-deploy-steps.md`](./references/ecs-deploy-steps.md)
- Container architecture and Dockerfile pitfalls: [`references/dockerfile-templates.md`](./references/dockerfile-templates.md)
- VKE pipeline sequencing (kubeconfig/addons/CR auth/rollout): [`references/vke-deploy-steps.md`](./references/vke-deploy-steps.md)
- Kubernetes readiness, LoadBalancer, probes, and manifest issues: [`references/k8s-manifests.md`](./references/k8s-manifests.md)
- Managed dependency wiring and migrations: [`references/supported-dependencies.md`](./references/supported-dependencies.md)
- veFaaS CLI/auth/framework setup: [`references/faas-deploy-steps.md`](./references/faas-deploy-steps.md) and `volcengine-vefaas`

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/k8s-manifests.md (reported line 353)May include surrounding context.

md
| Symptom | Cause | Fix |
|---|---|---|
| `CreateKubeconfig` returns `OperationDenied` | cluster not yet `Running` | Poll `ListClusters` until `Status.Phase=Running` before fetching the kubeconfig |
| `Service` `LoadBalancer` stuck at `<pending>` | missing CLB subnet annotation | Add `service.beta.kubernetes.io/volcengine-loadbalancer-subnet-id` to the Service |
| `BLB no available backend` / no available backend nodes | Pod readinessProbe failing, often because the probed `/health` path does not exist | Use the actual detected health path, or switch the probe to `tcpSocket`; diagnose with `kubectl describe pod` + `kubectl logs` |
| Container exits immediately with `exec format error` | image architecture does not match the VKE node architecture | Rebuild/pull/push with the node architecture (usually `linux/amd64`) and inspect the image platform before rollout (see [`dockerfile-templates.md`](./dockerfile-templates.md)) |

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/vke-deploy-steps.md (reported line 5)May include surrounding context.

md
Execution runbook for the VKE branch. The main `SKILL.md` keeps only the control-flow skeleton and hard boundaries; this file carries the command-level pipeline. Template details live in [`k8s-manifests.md`](./k8s-manifests.md) and [`dockerfile-templates.md`](./dockerfile-templates.md); for deeper CLI detail, activate the `volcengine-cli` skill and follow its VKE and CR guidance; a real end-to-end run is in `volcengine-iac/references/volcengine-vke-cr-nginx.md`.

Do not skip steps or reorder them. The most common failures come from running a later step before an earlier one converges (e.g. `kubectl apply` before the kubeconfig exists, or generating a Deployment before the image is pushed).

## Execution pipeline

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/vke-deploy-steps.md (reported line 16)May include surrounding context.

md
Do not hardcode node instance types. Build the image for the node architecture (default `linux/amd64` unless node-pool data proves otherwise).

### 2. Wait for the cluster, then fetch kubeconfig

Poll the cluster until it is running before any kubeconfig or workload call:

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/vke-deploy-steps.md (reported line 18)May include surrounding context.

2. Wait for the cluster, then fetch kubeconfig

Poll the cluster until it is running before any kubeconfig or workload call:

bash
for _ in $(seq 1 60); do

Chaining Abuse

High
Category
Tool Misuse
Confidence
75% confidence
Finding

Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.

Content

Scanner excerpt · references/dockerfile-templates.md (reported line 182)May include surrounding context.

md
RUN apk add --no-cache musl-dev
WORKDIR /app
COPY Cargo.toml Cargo.lock ./
RUN mkdir src && echo "fn main(){}" > src/main.rs && cargo build --release && rm -rf src
COPY . .
RUN touch src/main.rs && cargo build --release

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/dockerfile-templates.md (reported line 233)May include surrounding context.

text
.git
.gitignore
.env
.env.*
node_modules
__pycache__

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
85% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/ecs-deploy-steps.md (reported line 169)May include surrounding context.

run_cmd "upload-tos" 600 "mkdir -p /opt/$repo_name &&
curl --http1.1 --retry 5 --retry-all-errors --connect-timeout 10 --max-time 180 -L '$url' -o /tmp/app.tar.gz &&
tar -xzf /tmp/app.tar.gz -C /opt/$repo_name &&
rm /tmp/app.tar.gz"

text

Only pass the pre-signed URL into the remote command. Do not print it, put it in the resource ledger, include it in the final summary, or write it to README/log files. Reports and ledgers must record the durable `tos://bucket/key` object path instead. For cleanup, delete only the deployment prefix, for example `tosutil rm tos://bucket/prefix/ -r -f`; do not use `-y`.

Tool Parameter Abuse

High
Category
Tool Misuse
Confidence
85% confidence
Finding

Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).

Content

Scanner excerpt · references/ecs-deploy-steps.md (reported line 172)May include surrounding context.

rm /tmp/app.tar.gz"

text

Only pass the pre-signed URL into the remote command. Do not print it, put it in the resource ledger, include it in the final summary, or write it to README/log files. Reports and ledgers must record the durable `tos://bucket/key` object path instead. For cleanup, delete only the deployment prefix, for example `tosutil rm tos://bucket/prefix/ -r -f`; do not use `-y`.

### Pre-flight: agent readiness
Before any `RunCommand`, confirm the Cloud Assistant agent is `Running`:

Credential Access

High
Category
Privilege Escalation
Confidence
60% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

Scanner excerpt · references/ecs-deploy-steps.md (reported line 346)May include surrounding context.

md
User=appuser
Group=appuser
WorkingDirectory=/opt/__REPO_NAME__
EnvironmentFile=-/opt/__REPO_NAME__/.env
ExecStart=__EXEC_START__
Restart=always
RestartSec=5