Check provider logo

All Azure running container images in the subscription have no unresolved vulnerabilities

defender_container_images_resolved_vulnerabilities

Severitycritical
Servicedefender
by Prowler

Running container images are evaluated for unresolved vulnerability findings (CVEs) reported by Microsoft Defender for Cloud. The check reviews images currently in use across Kubernetes workloads and identifies where vulnerabilities remain unremediated.

Risk

Unremediated CVEs in active images enable:

  • RCE, container escape, and node takeover affecting integrity/availability
  • Data exfiltration and secret theft compromising confidentiality Adversaries can use public exploits to pivot across clusters and pipelines, tamper images, and disrupt services.
Run this check with Prowler CLI

prowler azure --checks defender_container_images_resolved_vulnerabilities

Recommendation

Adopt risk-based patching and least privilege:

  • Rebuild from updated bases; pin versions, avoid latest
  • Sign images; enforce admission control to block high-severity CVEs
  • Drop root, restrict capabilities, isolate networks
  • Continuously scan in CI/CD and at runtime; retire vulnerable images

Remediation

CLI

kubectl set image deployment/<DEPLOYMENT_NAME> <CONTAINER_NAME>=<PATCHED_IMAGE:TAG> -n <NAMESPACE>

Terraform
Other
  1. In the Azure portal, go to Microsoft Defender for Cloud > Recommendations
  2. Open "Azure running container images should have vulnerabilities resolved"
  3. Under Affected resources, select a running workload and view its vulnerable image findings
  4. Rebuild the image with patched packages or a newer base image and push it to your registry
  5. Go to your AKS cluster > Workloads > Deployments, edit the deployment, and update the container image to the patched tag; Save
  6. Wait for pods to roll out and Defender to rescan; the recommendation should turn Healthy after the next scan

Source Code

Resource Type

microsoft.security/assessmentssample

References