Check provider logo

Virtual machine is not created from an image affected by a known emerging threat

vm_emerging_threat_image

Severitycritical
Servicevm
by Prowler

Azure virtual machines are matched against threat signatures: emerging vulnerabilities described by the images that carry them (gallery or custom image name, marketplace publisher, offer and SKU, version range).

Signatures are supplied per scan under threat_signatures; Prowler Cloud supplies a maintained catalog to every scan.

Risk

A VM created from an affected image carries the vulnerability until it is patched or replaced. When the vulnerable service is reachable from the internet, a threat actor can exploit it remotely; for an authentication bypass, that means a shell, often as root, with no credential.

Run this check with Prowler CLI

prowler azure --checks vm_emerging_threat_image

Recommendation

Contain first by restricting the exposed port, then replace VMs built from affected images. The check reads the launch image, so after patching in place, mute the finding with a reason. Keep galleries and templates on current images, reach VMs through Azure Bastion or JIT access rather than open management ports, and treat a VM as compromised when unauthorized access cannot be ruled out.

Remediation

Other
  1. Read the threat named in the finding and its remediation
  2. Restrict the exposed port in the network security groups of the VM's network interfaces
  3. Patch the package on the VM and mute this finding once the fix is verified (the VM keeps its image), or recreate the VM from a fixed image
  4. Update gallery image versions and templates that still reference the affected image

Source Code

Resource Type

microsoft.compute/virtualmachines

References