Skip to content
StrikeOps

Kubernetes API or Dashboard Exposed

HighTypical severity Containers, CI/CD and source codeCWE-284ATT&CK T1133

01Description

The Kubernetes API server, dashboard or kubelet API was reachable from the internet or untrusted networks.

02Impact

Exposed control planes are targeted for cluster takeover and cryptomining. Anonymous access or a leaked token can give control of every workload and the secrets they hold.

03Severity

Typically

High

Typically High. Critical if anonymous or weakly authenticated access is allowed. High if the API is internet-reachable but properly authenticated.

04How to verify

  1. 1Identify Kubernetes API (6443), kubelet (10250) and dashboard endpoints.
  2. 2Test whether anonymous requests are allowed and what they return.
  3. 3Review RBAC for the anonymous and default service accounts.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Restrict API server access to private networks or authorized addresses.
  2. 2Disable anonymous authentication on the API server and kubelet.
  3. 3Remove the dashboard or place it behind strong authentication.
  4. 4Apply least-privilege RBAC.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo