🚀 Join our AI Wargame at Black Hat Asia and our Workshop + Wargame at NDC Sydney .


Missing Vulnerability Scanning for Container Images

Container images are not configured to be scanned for known vulnerabilities before deployment. Without image vulnerability scanning, insecure base images, outdated operating system packages, vulnerable application dependencies, or accidentally introduced pre-release/debug components may be promoted into production without detection.

This increases the risk that exploitable vulnerabilities are deployed into cloud workloads, where attackers may use them to gain unauthorised access, escalate privileges, access sensitive data, or compromise the availability and integrity of the application environment. Container images should be treated as release artefacts and validated through automated security scanning before they are deployed to production.

Remediation

Enable vulnerability scanning for container images. Where possible, enforce scanning as part of the CI/CD pipeline and block deployment of images that contain high or critical vulnerabilities. Ensure scan results are reviewed regularly, vulnerable images are rebuilt with patched base images and dependencies, and production deployments only use images that have passed security validation.

Metadata

  • Severity: high
  • Slug: missing-vulnerability-scanning-for-container-images

CWEs

  • 693: Protection Mechanism Failure
  • 1269: Product Released in Non-Release Configuration

OWASP

  • A05:2021: Security Misconfiguration

Available Labs

Open Gcp labs in SecDim Play for this vulnerability.

Deco line
Deco line

Play AppSec WarGames

Want to skill-up in secure coding and AppSec? Try SecDim Wargames to learn how to find, hack and fix security vulnerabilities inspired by real-world incidents.

Deco line
Deco line

Got a comment?

Join our secure coding and AppSec community. A discussion board to share and discuss all aspects of secure programming, AppSec, DevSecOps, fuzzing, cloudsec, AIsec code review, and more.

Read more