NASA CryptoLib
cpe:2.3:a:nasa:cryptolib:*:*:*:*:*:*:*
- <= 1.3.3
A heap buffer overflow vulnerability has been identified in CryptoLib versions through 1.3.3. The issue arises in the Crypto_TC_ApplySecurity function, where an incomplete validation of the frame length allows attackers to craft malicious frames. This exploitation causes a negative payload length, interpreted as a large unsigned value, leading to a buffer overflow during memory copying operations.
Exploitation of this vulnerability causes a heap buffer overflow, which can corrupt memory and potentially allow for remote code execution under certain conditions.
The vulnerability can be reproduced by sending a crafted frame with a specific length that triggers the buffer overflow. This can be done by using the Crypto_TC_ApplySecurity function with a frame length that, after the applied calculations, results in a negative value being interpreted as a large unsigned number. The buffer overflow can be verified by using AddressSanitizer, which will report the heap-buffer-overflow error.
Users are advised to update to version 1.4.0, where this vulnerability has been addressed.
Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.