Horizon Alert
Summary of the vulnerability and why it matters
A vulnerability in the Dokploy platform could allow unauthorized access to unrelated containers, sensitive logs, and host systems. This issue arises from how the platform handles service identification within its Docker terminal, container log, and monitoring features. The primary concern is confirming if Dokploy is used and if it is exposed to potential threats.
- Unauthorized access to container and host systems.
- Confirms Dokploy relevance and exposure.
- Assess Dokploy use and network exposure.
Attack Path
How an attacker could exploit the issue
An attacker with read access to any service in Dokploy could exploit this vulnerability by targeting unrelated containers. This could lead to obtaining a root shell within the Dokploy panel container, enabling access to other tenants' sensitive data and potentially compromising the entire host system through the mounted Docker socket.
- Requires read access to any service.
- Targets unrelated container via WebSocket handlers.
- Leads to host compromise and data access.
Live Threat
Current exploitation, exposure, and threat context
A low-privileged user with read access to any service could potentially gain root access to the Dokploy panel container. This access could allow them to read other tenants' logs and statistics, and use the mounted Docker socket to compromise the host system.
- Host system and tenant data at risk.
- Unauthorized access to container and host systems.
- Complete system compromise and data exposure.
Operational Fix
Recommended remediation, mitigation, and detection steps
Teams responsible for Dokploy, the self-hosted PaaS, should prioritize identifying all instances of the software, assessing their network exposure, and confirming business criticality. The first practical move is to locate all deployments, determine their reachability and importance, identify the accountable owner, and then plan remediation efforts based on the identified risks.
- Identify Dokploy deployments and owners.
- Verify network exposure and criticality.
- Plan remediation based on risk.