4Detailed findings
ANT-001
Dokploy panel open to the internet
Critical- Affected asset
- example.com:3000
- Category
- Exposed administration interface
Description
The Dokploy administration panel answers on port 3000 from any address on the internet. The panel manages every application, database and domain on the server.
Evidence
GET / HTTP/1.1
Host: example.com:3000
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
<title>Dokploy</title> (sign-in page returned)
Impact
An attacker can attack the sign-in page directly, by guessing passwords, reusing leaked ones or exploiting a flaw in the panel itself. A successful sign-in gives control of every application on the server and the secrets they use.
Remediation
- Block port 3000 in the server firewall.
- Reach the panel through an SSH tunnel or a VPN, or restrict it to trusted IP addresses.
- Use a strong, unique password for every panel account, and turn on two-factor authentication where it is available.
How to confirm the fix
From a network outside the server, a request to http://example.com:3000/ should time out or be refused.
ANT-002
Environment file readable from the browser
High- Affected asset
- https://example.com/.env
- Category
- Sensitive file exposure
Description
The application's environment file is served by the web server like any other static file. It can be downloaded without signing in.
Evidence
GET /.env HTTP/1.1
Host: example.com
HTTP/1.1 200 OK
Content-Type: text/plain
Content-Length: 412
DATABASE_URL=postgres://app:[redacted]@db:5432/app
SESSION_SECRET=[redacted]
PAYMENT_API_KEY=[redacted]
Impact
Anyone who downloads the file obtains the database credentials and the application secrets. Combined with ANT-003, the database can be read and changed directly.
Remediation
- Move the file out of the public folder and configure the web server to refuse requests for dotfiles.
- Treat every secret in the file as compromised and rotate it.
- Search the access logs for earlier requests to /.env to learn whether it has already been downloaded.
How to confirm the fix
A request to https://example.com/.env should return 403 or 404.
ANT-003
PostgreSQL accepts remote connections
High- Affected asset
- example.com:5432
- Category
- Exposed database service
Description
The PostgreSQL database listens on its default port and accepts connections from the public internet. Only the database password stands between an attacker and the data.
Evidence
$ pg_isready -h example.com -p 5432
example.com:5432 - accepting connections
Impact
The database can be attacked directly by password guessing. With the credentials exposed in ANT-002, it can be accessed immediately.
Remediation
- Remove the published port from the database container and let the application reach it over the internal network.
- If remote access is needed, allow only specific IP addresses in the firewall or use an SSH tunnel.
- Change the database password once the port is closed.
How to confirm the fix
From outside the server, a connection attempt to port 5432 should time out or be refused.
ANT-004
Traefik dashboard has no login
Medium- Affected asset
- example.com:8080
- Category
- Missing authentication
Description
The Traefik dashboard and its API are reachable on port 8080 without any authentication.
Evidence
GET /api/http/routers HTTP/1.1
Host: example.com:8080
HTTP/1.1 200 OK
Content-Type: application/json
[{"name":"app@docker","rule":"Host(`example.com`)", ...}]Impact
Anyone can list every route, service and internal hostname behind the proxy. This does not grant access by itself, but it gives an attacker a map of the server and makes further attacks easier to plan.
Remediation
- Turn off the insecure API mode in the Traefik configuration.
- If the dashboard is needed, publish it through a router protected by authentication and an IP allowlist.
How to confirm the fix
A request to http://example.com:8080/api/http/routers should be refused or require authentication.
ANT-005
Server header reveals software version
Low- Affected asset
- https://example.com/
- Category
- Information disclosure
Description
Responses from the web server include the exact nginx version in the Server header.
Evidence
HTTP/1.1 200 OK
Server: nginx/1.18.0
Impact
Knowing the exact version lets an attacker look up the weaknesses that apply to it and skip the ones that do not.
Remediation
- Set server_tokens off in the nginx configuration so the version is no longer sent.
- Keep nginx on a supported, up-to-date release.
How to confirm the fix
The Server header should read nginx, with no version number.