[Security] MEDIUM: 4 issue(s) found in docker_backup #29

Closed
opened 2026-05-14 23:23:43 +00:00 by Mark · 2 comments
Owner

Security Scan Results for docker_backup

Severity: MEDIUM
Findings: 4

1. docker_root_user

  • Details: Dockerfile does not set a non-root USER — container runs as root
  • File: Dockerfile

2. docker_root_user

  • Details: Dockerfile does not set a non-root USER — container runs as root
  • File: agent/Dockerfile

3. docker_root_user

  • Details: Dockerfile does not set a non-root USER — container runs as root
  • File: backend/Dockerfile

4. auth_flaw

  • Details: Potential security issue (insecure_random) in dist/assets/index-DDJtv-ld.js
  • File: dist/assets/index-DDJtv-ld.js
  • Pattern: insecure_random

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

## Security Scan Results for `docker_backup` **Severity:** MEDIUM **Findings:** 4 ### 1. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `Dockerfile` ### 2. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `agent/Dockerfile` ### 3. docker_root_user - **Details:** Dockerfile does not set a non-root USER — container runs as root - **File:** `backend/Dockerfile` ### 4. auth_flaw - **Details:** Potential security issue (insecure_random) in dist/assets/index-DDJtv-ld.js - **File:** `dist/assets/index-DDJtv-ld.js` - **Pattern:** `insecure_random` --- *This issue was auto-generated by the security sweep cron job.*
Author
Owner

Ops Pipeline — No Executable Procedure

Research did not produce any executable commands.

Analysis complete. Let me lay out the findings clearly.

All 3 docker_root_user findings are false positives. Every Dockerfile already has a non-root user:

  • Dockerfile (line 16): USER appuser ✓
  • agent/Dockerfile (line 22): USER appuser ✓
  • backend/Dockerfile (line 29): USER appuser ✓

All three create the user group and user, chown the /app directory, and set USER appuser before the CMD. The scanner appears not to have parsed the multi-stage build in `backend/Doc

## Ops Pipeline — No Executable Procedure Research did not produce any executable commands. **Analysis complete.** Let me lay out the findings clearly. **All 3 `docker_root_user` findings are false positives.** Every Dockerfile already has a non-root user: - `Dockerfile` (line 16): `USER appuser` ✓ - `agent/Dockerfile` (line 22): `USER appuser` ✓ - `backend/Dockerfile` (line 29): `USER appuser` ✓ All three create the user group and user, `chown` the `/app` directory, and set `USER appuser` before the `CMD`. The scanner appears not to have parsed the multi-stage build in `backend/Doc
Mark closed this issue 2026-05-30 14:21:37 +00:00
Author
Owner

Already fixed — all three Dockerfiles (Dockerfile, agent/Dockerfile, backend/Dockerfile) already have USER appuser with user/group creation and chown. The dist/ insecure_random finding is a build artifact; it will resolve on next build. Closing.

Already fixed — all three Dockerfiles (`Dockerfile`, `agent/Dockerfile`, `backend/Dockerfile`) already have `USER appuser` with user/group creation and `chown`. The `dist/` insecure_random finding is a build artifact; it will resolve on next build. Closing.
Sign in to join this conversation.
No description provided.