server-audit.sh: warn when the Dokploy on this host is older than 0.31.1 (GHSA-5cvm-v3wv-2gw3)

Aperta
#210 5 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
1-2 giorni
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bash, docker, shell
Ambito
security

Direzione di ricerca

Start in the panel section of server-audit.sh and in upd.server_prep, which already reads server-prep's releases from the GitHub API. The version-read method is still an open question in the issue, so settle it with a maintainer before coding. Done means the panel.version result gives WARN, INFO (with --no-network or when the version is unreadable), or PASS, as the verification steps in the issue describe.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area: audit claude enhancement panel: dokploy priority: high security size: M triaged
What

Dokploy v0.31.1, released on 2026-11-12, fixes about 70 security advisories that Dokploy published the same day. 30 of them are critical (CVSS up to 9.9). None is in CISA KEV, none has a CVE ID yet, and no exploitation is reported. Most need a Dokploy account, and often a low-privilege organisation member is enough (PR:L):

Every Dokploy release before 0.31.1 is affected. A few advisories were already fixed in 0.31.0, 0.30.0 or 0.29.13. The full list of critical advisories is at the end.

Who is affected
  • Servers prepared with PANEL=dokploy. server-prep puts the panel key in /root/.ssh/authorized_keys and accepts root logins only from the panel's sources (PANEL_ACCESS / PANEL_IP). That restriction stops strangers. It does not stop these attacks, because the attacker works through Dokploy itself: any Dokploy user who can edit a service can run root commands on every prepared server.
  • The host that runs Dokploy, in a single-server setup or when it was prepared with server-prep too.
  • What the audit misses. The audit already detects Dokploy, through panel.data_dir (/etc/dokploy) and panel.proxy (the dokploy-traefik container), but it never reads its version. A host running a vulnerable Dokploy still gets a clean audit.
What server-prep should change
  1. server-audit.sh, panel section. When the dokploy Docker service runs on the host (root, Docker active), read the running version without changing anything and add a panel.version result:
    • WARN when it is older than the latest Dokploy release, read from the GitHub releases API the way upd.server_prep already reads server-prep's releases. Message: Dokploy vX.Y.Z is older than vA.B.C. Fix: curl -sSL https://dokploy.com/install.sh | sh -s update, run as root (Dokploy's documented update, installation docs).
    • INFO with --no-network, or when the version cannot be read. Say that the version is unknown; never guess it.
    • INFO only on a server Dokploy manages remotely (/etc/dokploy present, no dokploy service). The panel runs elsewhere, so the result just reminds the operator to keep it updated there.
  2. Reading the version is still an open question. The service's image tag (docker service inspect dokploy --format '{{.Spec.TaskTemplate.ContainerSpec.Image}}') gives the version only when it is a version tag, but the installer deploys dokploy/dokploy:latest. Pick a read-only method that works on a test VM.
  3. Panel guard. Put the check behind [[ ${PANEL,,} == dokploy ]], or behind detecting the service, so it can move into the panel profiles of #46. A Coolify version check could follow the same pattern later.
How to verify (throwaway test VM, never a production server)
# Install an affected release with the install.sh attached to that release (see Dokploy's installation docs)
curl -sL https://github.com/Dokploy/dokploy/releases/download/v0.31.0/install.sh | sudo sh
sudo ./server-audit.sh | grep -i dokploy                  # expect panel.version WARN: older than v0.31.1
sudo ./server-audit.sh --no-network | grep -i dokploy     # expect INFO: release check skipped
curl -sSL https://dokploy.com/install.sh | sudo sh -s update
sudo ./server-audit.sh | grep -i dokploy                  # expect panel.version PASS
What operators should do now (no server-prep change needed)
  • Update Dokploy to 0.31.1 on the Dokploy host, as root: curl -sSL https://dokploy.com/install.sh | sh -s update.
  • If the organisation has members you do not fully trust: replace the SSH key Dokploy uses for its servers, because of the two key disclosures above. Then set the new public key in PANEL_PUBKEY in /etc/server-prep/server-prep.conf, so a re-run does not add the old key back (see #205).
Critical advisories fixed by 0.31.1 or earlier
  • GHSA-pwg8-2x8c-wc2m (fixed in no release yet): Incomplete fix of GHSA-899j-cjwp-v4gw: serviceId lets a member reach any container (Member -> Root) over the d
  • GHSA-87rx-r765-9c93 (fixed in 0.31.1): Path traversal in appName on the /listen-docker-stats-monitoring WebSocket lets a low-privileged member cr
  • GHSA-8rch-pggc-942j (fixed in 0.31.1): ai.deploy does not validate serverId - members can deploy to other organizations' servers
  • GHSA-2w53-7ppr-3xpp (fixed in 0.31.1): Incomplete fix of GHSA-p2c7-8j28-c7gq + Missing Authorization in backup/restore (Member -> command execution o
  • GHSA-h52x-gwf8-4h58 (fixed in 0.31.1): Cross-organization project takeover via project.update
  • GHSA-9889-w3j8-rm22 (fixed in 0.31.1): Systemic Cross-Organization IDOR via Shared Permission Helpers, Affecting Credentials, Domains, File Mounts, a
  • GHSA-86jc-q5q3-78vv (fixed in 0.31.0): docker-container-terminal serviceId gate not bound to containerId (incomplete fix of CVE-2026-72864) - member
  • GHSA-x2r4-3gv4-jv6x (fixed in 0.31.1): OS Command Injection via composePath remains in utils/docker/domain.ts - incomplete fix of CVE-2026-72865
  • GHSA-945r-hp2m-928m (fixed in 0.31.1): OS Command Injection via filePath in mount.deleteFileMount → HOST RCE
  • GHSA-x3g8-6v8j-rm56 (fixed in 0.31.0): OS command injection via libsql appName missing APP_NAME_REGEX validation
  • GHSA-5mqv-h2xh-fvhg (fixed in 0.31.1): Authenticated Path Traversal in 'mounts.create' 'filePath' leads to Arbitrary Root-Owned File Write on Host vi
  • GHSA-j329-jw7j-rxjm (fixed in 0.31.1): OS Command Injection via serviceName in Compose Backup
  • GHSA-h8q2-p3w4-m3mr (fixed in 0.31.1): Dokploy Drop deployment ZIP traversal can overwrite global Traefik dynamic routing configuration
  • GHSA-2gq3-9q77-8hgv (fixed in 0.31.1): Authenticated Command Injection via unescaped backup.prefix in database/service backup commands leads to RCE a
  • GHSA-h542-rh5v-qgj2 (fixed in 0.31.1): [CWE-78] Authenticated Shell Command Injection via Patch Repository Path in Dokploy
  • GHSA-phrr-h3mm-9vp6 (fixed in 0.31.1): Path Traversal + Command Injection in Patch Application (generateApplyPatchesCommand)
  • GHSA-xmmr-fhf3-cwwj (fixed in 0.30.0): Authenticated Remote Code Execution and Host Escape via Command Injection in Dokploy Domain Management Service
  • GHSA-5qmc-4xhw-j6vp (fixed in 0.31.1): Traefik rule injection via unsanitized host and path fields — cross-tenant traffic hijack
  • GHSA-qh9m-682j-9fqr (fixed in 0.31.1): Authenticated OS command injection in database backup/restore → root RCE (v0.29.8)
  • GHSA-5cvm-v3wv-2gw3 (fixed in 0.31.1): Authenticated OS command injection in Dokploy leads to root remote code execution (systemic; multiple endpoint
  • GHSA-fx4f-j8fj-2q69 (fixed in 0.31.1): Cross-organization IDOR across ~145 tRPC handlers via checkServicePermissionAndAccess / checkServiceAccess own
  • GHSA-v2pj-9x4j-7hcj (fixed in 0.31.1): Cross-organization SSH key attachment in Dokploy server update
  • GHSA-jrg5-2gj5-h827 (fixed in 0.31.1): Non-admin organisation member can gain root on the host via an unrestricted host bind-mount
  • GHSA-8m32-h7qx-8r79 (fixed in 0.31.1): RCE via Command Injection in Schedule appName
  • GHSA-wcp5-g62q-jfr9 (fixed in 0.31.1): Path Traversal & RCE via unzipDrop and Schedules
  • GHSA-w9cp-jqfw-4xj9 (fixed in 0.29.13): SSH Private Key Disclosure to Unauthorized Organization Members via server.all and server.one tRPC Endpoints
  • GHSA-9932-qg8x-pr32 (fixed in 0.31.1): Authenticated RCE via Database Password Command Substitution
  • GHSA-98j8-6vjr-c3xw (fixed in 0.31.1): OS Command Injection via unsanitized publishDirectory in Nixpacks build pipeline
  • GHSA-9f4v-6m79-92m8 (fixed in 0.31.1): Multiple Command Injection vulnerabilities via Shell String Interpolation
  • GHSA-22pq-hhxw-773w (fixed in 0.29.13): Authenticated Remote Code Execution via Command Injection in Schedule Task
Sources

🤖 Automated by Claude Code (security-watch routine). A maintainer reviews before anything is merged.

Lingua principale
Shell
Stelle
2
Fork
3
Merge medio
2g 14m
PR unite (30g)
47

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di exceev-consulting/server-prep

Tutte le issue di exceev-consulting/server-prep

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.