Ganeti's small web count sits in front of a high-impact management plane
Ganeti manages virtual-machine clusters and depends on a trusted internal environment. Its Remote API supports cluster inspection and operations, while the master and node daemons handle privileged work. A public Ganeti interface is not equivalent to a public web application with read-only display data.
The ZoomEye observations on 2026-11-16 used sub_type=all, page 1, and pagesize 1. app="Ganeti" returned 1, title="Ganeti" returned 5, and http.body="Ganeti" returned 96. The small numbers make the topic precise: one application match is a lead worth verifying carefully, not a representative population.
| Query role | Exact dork | Observed total |
|---|---|---|
| Application fingerprint | app="Ganeti" |
1 |
| Page title | title="Ganeti" |
5 |
| HTTP body | http.body="Ganeti" |
96 |
Read the product documentation before scanning
The Ganeti 3.0 security guide says the software was designed for internal, trusted systems and that its security model is all-or-nothing. The RAPI binds to all interfaces by default and permits read-only requests without authentication. The guide recommends network restriction or the --require-authentication flag when the API must be reachable.
Those statements change how an asset should be handled. A read-only cluster state can reveal instance names, addresses, and topology. A write-capable API path may affect cluster operations. The monitoring daemon is also described as unencrypted and unauthenticated in the current guide, with firewall rules recommended.
Count only after the owner is known
The application result should be matched to an owned certificate, hostname, and cluster record. A website that mentions Ganeti is not the RAPI. A certificate subject may identify a management load balancer rather than the cluster master.
Do not send cluster-changing requests during discovery. Confirm access only with authorized test accounts and a documented maintenance window. If a candidate is outside the organization's ownership, stop at passive classification and use the appropriate disclosure process.
Review the network boundary
The security review should list every Ganeti-related listener: RAPI, monitoring daemon, confd, node RPC, SSH, and DRBD traffic. For each, record the bind address, firewall rule, authentication requirement, TLS configuration, and allowed source networks.
RAPI access should be limited to operators and automation that need it. Read-only access without authentication is still an information exposure if an unintended network can reach it. Monitoring endpoints need the same treatment because topology and status can support later intrusion activity.
Treat the one fingerprint as a case study
The exact application match could be a management endpoint, a demo, a labelled service, or a false positive. The five title matches and 96 body matches are weaker pools. None should be called a vulnerable cluster.
A useful outcome is a verified owner, a network diagram, and a change record for any exposed management listener. The small count makes manual review practical. It also shows why a low number is not a reason to skip the investigation when the component controls infrastructure.
Top comments (0)