This article catalogs passive and active attack classes against the communication channel between AWS Nitro Enclaves and AWS KMS. Passive attacks include data swap attacks on encrypted data keys, CMK substitution via manipulable metadata, key commitment issues, and replay attacks within the 5-minute attestation validity window. Active attacks exploit the lack of cryptographic binding between attestation documents and request parameters, requiring enclave-initiated TLS with a pinned CA for mitigation. The authors also identify vulnerabilities in the aws-nitro-enclaves-sdk-c library and recommend alternative SDKs.
cryptographic attacks
1 post
A few notes on AWS Nitro Enclaves: KMS integration