Custom IVs with non-compliant length for AES key wrap in AWS CloudHSM

Your application uses PKCS #11 library

The PKCS #11 library is installed as the libpkcs11.so file in your /opt/cloudhsm/lib folder. Applications written in the C language generally use the PKCS #11 library directly, while application written in Java may be using the library indirectly via a Java abstraction layer. If you're using Windows, you are NOT affected, as PKCS #11 library is not presently available for Windows.

Your application specifically uses version 3.0.0 of the PKCS #11 library

If you received an email from the AWS CloudHSM team, you are likely using version 3.0.0 of the PKCS #11 library.

To check the software version on your application instances, use this command:

rpm -qa | grep ^cloudhsm

You wrap keys using AES key wrapping

AES key wrapping means you use an AES key to wrap out some other key. The corresponding mechanism name is CKM_AES_KEY_WRAP. It is used with the function C_WrapKey. Other AES based wrapping mechanisms that use initialization vectors (IVs), such as CKM_AES_GCM and CKM_CLOUDHSM_AES_GCM, are not affected by this issue. Learn more about functions and mechanisms.

You specify a custom IV when calling AES key wrapping, and the length of this IV is shorter than 8

AES key wrap is generally initialized using a CK_MECHANISM structure as follows:

CK_MECHANISM mech = {CKM_AES_KEY_WRAP, IV_POINTER, IV_LENGTH};

This issue applies to you only if: