server-audit.sh: warn when the Dokploy on this host is older than 0.31.1 (GHSA-5cvm-v3wv-2gw3)
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
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
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):
- Root command execution on the Dokploy host and, over SSH, on every server it manages. Dokploy runs these commands on managed servers through
execAsyncRemoteas their SSH user, which is typically root. Examples: GHSA-5cvm-v3wv-2gw3, GHSA-qh9m-682j-9fqr, GHSA-9f4v-6m79-92m8. - Any member could read the managed servers' SSH private keys: GHSA-w9cp-jqfw-4xj9 (fixed in 0.29.13) and GHSA-rwpf-vrr8-6g7c (high, fixed in 0.31.1).
- A member without Docker access gets root on the host through a host bind-mount: GHSA-jrg5-2gj5-h827.
- Cross-organisation access: GHSA-fx4f-j8fj-2q69 and GHSA-9889-w3j8-rm22.
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_keysand 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) andpanel.proxy(thedokploy-traefikcontainer), but it never reads its version. A host running a vulnerable Dokploy still gets a clean audit.
What server-prep should change
- server-audit.sh, panel section. When the
dokployDocker service runs on the host (root, Docker active), read the running version without changing anything and add apanel.versionresult:- WARN when it is older than the latest Dokploy release, read from the GitHub releases API the way
upd.server_prepalready 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/dokploypresent, nodokployservice). The panel runs elsewhere, so the result just reminds the operator to keep it updated there.
- WARN when it is older than the latest Dokploy release, read from the GitHub releases API the way
- 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 deploysdokploy/dokploy:latest. Pick a read-only method that works on a test VM. - 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_PUBKEYin/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
appNameon the/listen-docker-stats-monitoringWebSocket lets a low-privileged member cr - GHSA-8rch-pggc-942j (fixed in 0.31.1):
ai.deploydoes 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
- Dokploy v0.31.1 release: https://github.com/Dokploy/dokploy/releases/tag/v0.31.1
- Dokploy security advisories: https://github.com/Dokploy/dokploy/security/advisories
- Dokploy update procedure: https://docs.dokploy.com/docs/core/installation (section "Updating Dokploy") and https://docs.dokploy.com/docs/core/manual-installation (section "Manual Upgrade")
🤖 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
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di exceev-consulting/server-prep
-
area: docs bug claude documentation good first issue priority: low size: S triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
exceev-consulting/server-prep#225 ·
I maintainer di solito rispondono entro 2 giorni
-
area: preconfig bug claude priority: medium size: S triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
exceev-consulting/server-prep#224 ·
I maintainer di solito rispondono entro 2 giorni
-
claude enhancement priority: low size: S
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
exceev-consulting/server-prep#222 ·
I maintainer di solito rispondono entro 2 giorni
-
e2e flake: boot fails on debian-13 when its genericcloud image is missing from SHA512SUMSForse già presa @exceev-claude l’ha presa 1 giorno fa. Apertaarea: ci bug claude priority: high size: S
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
exceev-consulting/server-prep#212 · 2 commenti ·
I maintainer di solito rispondono entro 2 giorni
-
server-audit.sh: flag world-writable directories in /etc such as /etc/dokploy (GHSA-qxjv-6cvh-32c6)Apertaarea: audit claude enhancement panel: dokploy priority: high security size: S triaged
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
exceev-consulting/server-prep#211 ·
I maintainer di solito rispondono entro 2 giorni
Tutte le issue di exceev-consulting/server-prep
Issue simili
-
bot-found documentation priority: P3
Difficoltà 1/5 1-3 ore Idoneità per principianti 88/100
madenvel/KalinkaPlayer#602 ·
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
huggingface/kernels#1006 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 94/100
I maintainer di solito rispondono entro 2 giorni
-
severity: low
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
luainkernel/lunatik#2594 ·
I maintainer di solito rispondono entro 1 giorno