VSOCK-01: Vsock service exposure¶
| Property | Value |
|---|---|
| Severity | medium |
| Platform | AWS Nitro Enclaves |
| Lifecycle stage | runtime |
| Policy | P-06: Host-supplied inputs are authenticated |
| Mode | Active: runs fixed read-only commands on the host. Skipped with --read-only. |
What it checks¶
It passes when:
- No vsock listeners found on the host.
Example failures:
- … vsock listener(s) found on the host. Verify each service requires authentication before processing requests.
- 3 vsock listener(s) found on the host. Verify each service requires authentication.
How to fix¶
- Ensure every vsock service validates caller identity before processing requests. Unauthenticated RPC methods exposed over vsock allow host-side extraction of enclave metadata, keys, and operational state.
After the fix, scan again: the check should report PASS.
When it is not assessed¶
SKIP:
- No instance ID specified; skipping check.
Scan inputs¶
The untrust scan options this check reads:
| Option | Description |
|---|---|
--instance-id |
EC2 instance ID running the Nitro Enclave. |
--region |
AWS region. |
Permissions¶
The cloud API calls this check makes, read from the scanner's source:
| Cloud | API call | Permission | Access |
|---|---|---|---|
| AWS | ssm.get_command_invocation |
ssm:GetCommandInvocation |
read |
| AWS | ssm.send_command |
ssm:SendCommand |
run command |
Every AWS scan also calls sts:GetCallerIdentity. See Required permissions for a complete policy.
Related¶
- Other checks for policy P-06: DNS-01, ENV-01, GPUCC-INPUT-01
Evidence recorded¶
Keys in the finding's evidence: vsock_listeners
Generated from untrust 1.3.0 (commit 7ef462d9a0c3).