[Security] MEDIUM: 5 issue(s) found in clawdeploy #8

New issue

Closed

opened 2026-05-14 23:23:49 +00:00 by Mark · 2 comments

Mark commented

2026-05-14 23:23:49 +00:00

Owner

Security Scan Results for `clawdeploy`

Severity: MEDIUM
Findings: 5

1. docker_root_user

Details: Dockerfile does not set a non-root USER — container runs as root
File: deploy/docker/self-contained/Dockerfile

2. docker_root_user

Details: Dockerfile does not set a non-root USER — container runs as root
File: deploy/docker/probe-worker/Dockerfile

3. docker_root_user

Details: Dockerfile does not set a non-root USER — container runs as root
File: deploy/docker/smart-worker/Dockerfile

4. docker_root_user

Details: Dockerfile does not set a non-root USER — container runs as root
File: deploy/docker/callback-worker/Dockerfile

5. docker_root_user

Details: Dockerfile does not set a non-root USER — container runs as root
File: deploy/docker/news-worker/Dockerfile

This issue was auto-generated by the security sweep cron job.

## Security Scan Results for `clawdeploy` **Severity:** MEDIUM **Findings:** 5 ### 1. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `deploy/docker/self-contained/Dockerfile` ### 2. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `deploy/docker/probe-worker/Dockerfile` ### 3. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `deploy/docker/smart-worker/Dockerfile` ### 4. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `deploy/docker/callback-worker/Dockerfile` ### 5. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `deploy/docker/news-worker/Dockerfile` --- *This issue was auto-generated by the security sweep cron job.*

Mark added the

blocked:no-procedure

label

2026-05-15 20:25:05 +00:00

Mark commented

2026-05-16 09:26:20 +00:00

Author

Owner

Ops Pipeline — No Executable Procedure

Research did not produce any executable commands.

IS_OPS: NO

HOST: localhost

STATUS: NOT_OPS

EVIDENCE: All 5 findings report the same issue — Dockerfiles missing a non-root USER directive. This is a code change to Docker build definitions (adding USER picoclaw or similar after RUN instructions). Per the definition:

OPS = installing, configuring, deploying, API calls, service management, infrastructure changes, backups, restores, SSH, cron jobs
NOT OPS = refactoring code, implementing new features, bug fixes

## Ops Pipeline — No Executable Procedure Research did not produce any executable commands. **IS_OPS: NO** **HOST:** localhost **STATUS:** NOT_OPS **EVIDENCE:** All 5 findings report the same issue — Dockerfiles missing a non-root `USER` directive. This is a code change to Docker build definitions (adding `USER picoclaw` or similar after `RUN` instructions). Per the definition: - **OPS** = installing, configuring, deploying, API calls, service management, infrastructure changes, backups, restores, SSH, cron jobs - **NOT OPS** = refactoring code, implementing new features, bug fixes

Mark added

triage-approved

quickfix

and removed

blocked:no-procedure

labels

2026-05-28 07:21:36 +00:00

Mark closed this issue

2026-05-30 14:24:23 +00:00

Mark commented

2026-05-30 14:24:27 +00:00

Author