Trail of Bits Researchers Uncover Security Weaknesses in AWS Nitro Enclaves and KMS Integration
Trail of Bits researchers have identified passive and active attack vectors targeting the communication channel between AWS Nitro Enclaves and AWS Key Management Service (KMS), alongside vulnerabilities in the AWS Nitro Enclaves SDK for C.
Trail of Bits researchers have detailed significant security concerns regarding the integration of AWS Nitro Enclaves with AWS Key Management Service (KMS). In their latest analysis, the third in a series on Nitro Enclaves, the team outlines both passive and active attack vectors that can compromise the communication channel between these two services. This research highlights that even within the same cloud provider's ecosystem, integrating sensitive services like KMS with trusted execution environments like Nitro Enclaves introduces novel threat landscapes.
The analysis delves into the intricacies of KMS, explaining its role as a Hardware Security Module (HSM) service that supports various key types, including Customer-managed keys (CMKs), data keys, and data key pairs. It details how developers typically use KMS for operations like envelope encryption, where sensitive data keys are encrypted by CMKs, ensuring that CMKs themselves never leave the secure KMS environment. The research also touches upon the access control mechanisms, such as key policies and IAM policies, that govern how these keys can be utilized.
A core focus of the report is the communication channel between Nitro Enclaves and KMS. Two primary mechanisms are discussed: KMS policies that restrict access to CMKs based on enclave attestation documents (specifically, PCR values), and KMS encrypting responses to the enclave's public keys. These mechanisms are intended to ensure that only authorized enclaves can access specific keys and that sensitive data returned by KMS is protected. However, the researchers found that certain KMS operations, like Encrypt, are not supported with these attestation-based security features, potentially limiting secure cryptographic operations within enclaves.
The study further explores common use cases for integrating KMS with Nitro Enclaves, such as enhancing application-specific security, signing enclave image files (EIFs), and increasing entropy within the enclave. For instance, restricting KMS key access based on PCR values ensures that only specific enclave versions can access sensitive data, a crucial aspect for authenticated external storage. The ability to sign EIFs using KMS-protected keys also adds a layer of developer identity protection.
Beyond the communication channel, Trail of Bits disclosed specific vulnerabilities within the AWS Nitro Enclaves SDK for C. While the exact nature of these SDK vulnerabilities is not fully detailed in the provided text, their existence suggests potential weaknesses in how applications interact with Nitro Enclaves, potentially leading to insecure data handling or unintended information disclosure.
The researchers recommend safer alternatives for integrating trusted enclaves with KMS, implying that current default configurations or SDK implementations may not offer adequate protection against the identified threats. This advice is critical for organizations relying on Nitro Enclaves for sensitive workloads and key management.
In conclusion, the findings from Trail of Bits underscore the importance of rigorous security analysis for cloud-native security services. While Nitro Enclaves and KMS offer powerful security features, their integration requires careful consideration of potential attack vectors and vulnerabilities in both the communication protocols and the supporting SDKs. Organizations using these services are advised to review their configurations and consider the security implications highlighted by this research.