Back to all scenarios
Scenario #244
Security
K8s v1.20, AWS EKS
Use of Insecure Container Images
Insecure container images were used in production, leading to the deployment of containers with known vulnerabilities.
Find this helpful?
What Happened
Containers were pulled from an untrusted registry that did not implement image scanning. These images had known security vulnerabilities, which were exploited once deployed in the cluster.
Diagnosis Steps
- 1Reviewed container image sourcing and found that some images were pulled from unverified registries.
- 2Scanned the images for vulnerabilities and identified several critical issues, including outdated libraries and unpatched vulnerabilities.
Root Cause
Use of untrusted and insecure container images led to the deployment of containers with vulnerabilities.
Fix/Workaround
• Enforced the use of trusted container image registries that support vulnerability scanning.
• Integrated image scanning tools like Trivy or Clair into the CI/CD pipeline to identify vulnerabilities before deployment.Lessons Learned
Always verify and scan container images for vulnerabilities before using them in production.
How to Avoid
- 1Use trusted image registries and always scan container images for vulnerabilities before deploying them.
- 2Implement an image signing and verification process to ensure image integrity.