How to fix: etcd API Reachable Without Client Certificate Authentication
The response body matches etcd's own /version endpoint format: an etcdserver version string and an etcdcluster version string returned together in the same JSON object. This field pairing is unique to etcd's version handler and confirms the etcd API is answering requests without a client certificate.
Why it matters
etcd is the datastore behind every Kubernetes cluster's objects, including Secrets, which by default are stored base64-encoded rather than encrypted. An etcd API that answers unauthenticated requests at all almost always means client certificate (mTLS) enforcement is missing at the listener level for every endpoint, including the key-value read/write API, granting full read and write access to cluster state.
etcd's security model relies on mutual TLS: every client, including etcd itself in a cluster, must present a certificate signed by the cluster's CA. If the listener accepts a plain request without a certificate at all, that policy is not being enforced anywhere on that port, not just on this one endpoint.
How to fix it
- 1Require client certificate authentication on the etcd client port: set --client-cert-auth=true with --trusted-ca-file pointing at the cluster CA.
- 2Never expose etcd's client port (2379) to a network wider than the control plane nodes that need it.
- 3Restrict access with a firewall/security group to only the Kubernetes API server(s) and etcd peers.
- 4If this instance was found open, rotate every Secret stored in the cluster and audit etcd's access logs for unauthorized reads.
Code examples
etcd flags: require client certificates
etcd \
--client-cert-auth=true \
--trusted-ca-file=/etc/etcd/pki/ca.crt \
--cert-file=/etc/etcd/pki/server.crt \
--key-file=/etc/etcd/pki/server.key \
--listen-client-urls=https://10.0.0.5:2379References
Detected automatically by VulnRadar. The check id is etcd-api-exposed, stable across every scan so you can filter or diff on it.
More info disclosure checks
- MediumRails Session Cookie Missing HttpOnly Flag
- InfoServer header truncated
- InfoPHP session cookie naming exposes runtime
- Infoconfig.js / settings.js referenced (verify contents)
- Infoenv.js / environment.js referenced (verify contents)
- InfoSitemap.xml publicly accessible
- InfoOpenAPI schema version exposed in URL
- LowCORS exposes internal CDN hostname
Questions
- How severe is etcd API Reachable Without Client Certificate Authentication?
- VulnRadar rates this critical severity in the info disclosure category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id etcd-api-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does etcd API Reachable Without Client Certificate Authentication map to?
- It maps to CWE-306. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.