Outdated and Vulnerable Cluster Add-ons

Outdated and Vulnerable Cluster Add-ons

An ingress controller nobody upgraded reads every Secret.

What Is Outdated and Vulnerable Cluster Add-ons?

Cluster add-ons like the ingress controller, the CNI and CSI drivers face the internet, carry their own CVEs, and by default no app team owns them. You'll fingerprint an ingress controller several minor versions behind, watch a published remote code execution reach its service account and read every Secret in the cluster, then inventory the add-ons, upgrade the controller, cut what its account can reach, rotate the exposed Secrets and add an admission policy that refuses images with known critical vulnerabilities. Maps to the OWASP Kubernetes Top Ten 2022 risk Outdated and Vulnerable Kubernetes Components.

What You'll Learn in Outdated and Vulnerable Cluster Add-ons

Outdated and Vulnerable Cluster Add-ons — Training Steps

  1. The add-ons nobody upgrades

    Today Bob is targeting Tulverra, an online marketplace. Its storefront and checkout run on Kubernetes, and its API server turned him away without a credential. So he looks at the software around the apps instead: the ingress controller, the CNI, the CSI drivers. These add-ons face the internet and run on their own release schedule, and in most clusters no app team owns them. He starts by fingerprinting the ingress controller that answers for tulverra.com.

  2. A version is enough to find the exploit

    Bob does not fuzz for a bug. He looks the version up. A published vulnerability for the exact release tells him what is already written and waiting.

  3. Code execution in the controller

    Bob runs the published proof-of-concept. The exploit payload itself is not reproduced here; what matters for defence is where it lands and what that identity can reach. The controller pod runs as its own ServiceAccount, and that account is the real prize.

  4. Read every Secret in the cluster

    The controller needs to read the TLS Secrets its Ingress objects reference, so its ServiceAccount is granted read on Secrets across the whole cluster. Bob now holds that account.

  5. What the Secrets unlock

    Bob decodes the storefront's session signing key. It is the HMAC key the storefront uses to sign every login session.

  6. Check your understanding

  7. Forged sessions, traced to the controller

    Tulverra's platform-security lead has linked a run of forged logins and a leaked TLS certificate back to the ingress controller, and to the version it runs.

  8. Inventory the add-ons

    Noor is right that nobody owns these. Alice lists every add-on running across the cluster with the image tag each one is pinned to.

  9. Which ones are out of support

    A version on its own does not say whether it is safe. Alice checks each add-on against its supported releases and the critical vulnerabilities published for it.

  10. Open the controller's values

    The controller is installed from a chart whose values pin the image tag. Alice opens the values file the cluster actually runs.

Security Framework Coverage

OWASP Kubernetes Top 10

  • K10:2022 Outdated and Vulnerable Kubernetes Components

CWE

  • CWE-1104 Use of Unmaintained Third Party Components
  • CWE-1395 Dependency on Vulnerable Third-Party Component

MITRE ATT&CK

  • T1190 Exploit Public-Facing Application
  • T1552.007 Unsecured Credentials: Container API

CIS Controls

  • CIS 7 Continuous Vulnerability Management
  • CIS 4 Secure Configuration of Enterprise Assets and Software

NIST CSF

  • PR.AT-02 Individuals in specialized roles are provided with awareness and training so that they possess the knowledge and skills to perform relevant tasks with cybersecurity risks in mind
  • ID.RA Risk Assessment
  • PR.PS Platform Security

NICE Framework

  • IO-WRL-005 Systems Administration
  • DD-WRL-001 Cybersecurity Architecture