Back to all scenarios
Scenario #248
Security
K8s v1.19, AWS EKS
Use of Deprecated APIs with Known Vulnerabilities
The cluster was using deprecated Kubernetes APIs that contained known security vulnerabilities, which were exploited by attackers.
Find this helpful?
What Happened
Kubernetes components and applications in the cluster were using deprecated APIs, which were no longer supported and contained known security issues. The attacker exploited these vulnerabilities to gain unauthorized access to sensitive resources.
Diagnosis Steps
- 1Reviewed the API versions used by the cluster components and identified deprecated APIs.
- 2Scanned cluster logs and found unauthorized access attempts tied to these deprecated API calls.
Root Cause
Outdated and deprecated APIs were used, exposing the cluster to security vulnerabilities that were no longer patched.
Fix/Workaround
• Upgraded Kubernetes components and applications to use supported and secure API versions.
• Removed deprecated API usage and enforced only supported versions.Lessons Learned
Always stay current with supported APIs and avoid using deprecated versions that may not receive security patches.
How to Avoid
- 1Regularly check Kubernetes API deprecation notices and migrate to supported API versions.
- 2Set up monitoring to detect the use of deprecated APIs in your cluster.