Check provider logo

Confidential-workload host does not expose likely vsock-proxy TCP ports to the internet

ec2_confidential_workload_host_vsock_proxy_exposed

Severitymedium
Serviceec2
by Prowler
internet-exposed

Hosts of Nitro Enclave workloads are evaluated for unrestricted ingress on TCP ports commonly used by vsock-proxy applications (enclave_vsock_ports, default [5000, 8000-8090, 9000]). vsock is AF_VSOCK, but proxy applications bridge to TCP; this heuristic targets the bridge. Assesses the host environment only.

Risk

Publicly reachable vsock-proxy TCP ports let an attacker interact with the proxy and potentially reach the enclave communication channel the host was expected to keep private.

Run this check with Prowler CLI

prowler aws --checks ec2_confidential_workload_host_vsock_proxy_exposed

Run in Prowler Cloud

Recommendation

Keep any TCP bridge to vsock off the public internet on confidential-workload hosts. Because this control is heuristic, review flagged ports against the actual proxy scheme before broad remediation.

Remediation

CLI

aws ec2 revoke-security-group-ingress --group-id <sg-id> --protocol tcp --port <port> --cidr 0.0.0.0/0

Native IaC
Terraform
Other
  1. Confirm which TCP ports the vsock-proxy actually needs on the host.
  2. Restrict ingress to those ports to internal CIDRs or peer security groups only.
  3. Adjust enclave_vsock_ports in the audit config if the deployment uses a non-default proxy scheme.

Source Code

Resource Type

AwsEc2Instance

References