NASA CryptoLib before 1.3.2 does not check whether the SA is in an operational state before use, possibly leading to a bypass of the Space Data Link Security protocol (SDLS)

NASA CryptoLib before 1.3.2 uses Extended Procedures that are a Work in Progress (not intended for use during flight), potentially leading to a keystream oracle

Heap Buffer Overflow via Incomplete Length Check in `Crypto_TC_ApplySecurity`

CryptoLib's Crypto_TC_Prep_AAD Has Buffer Overflow Due to Integer Underflow

CryptoLib Has Heap Buffer Overflow Due to Unsigned Integer Underflow in Crypto_TC_ProcessSecurity

CryptoLib Has Heap Buffer Overflow in Crypto_AOS_ProcessSecurity Function

CryptoLib's Crypto_TC_ApplySecurity() Has a Heap Buffer Overflow Vulnerability

CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length