CVE Intelligence

Vulnerabilidades do Timlegge Crypt::nacl::sodium

🔔 Criar alerta RSS Verificador de versão

CVEs publicadas que afetam Timlegge Crypt::nacl::sodium: 2 registro(s), com versões afetadas e correções.
cpe:2.3:a:timlegge:crypt::nacl::sodium

CVE-2026-30909 Crítica · 9.8 CWE-190 07/03/2026
Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows
Crypt::NaCl::Sodium versions through 2.002 for Perl has potential integer overflows. bin2hex, encrypt, aes256gcm_encrypt_afternm and seal functions do not check that output size will be less than SIZE_MAX, which could lead to integer wraparound causing an undersized output buffer. Encountering this issue is unlikely as the message length would need to be very large. For bin2hex() the bin_len would have to be > SIZE_MAX / 2 For encrypt() the msg_len would need to be > SIZE_MAX - 16U For aes256gcm_encrypt_afternm() the msg_len would need to be > SIZE_MAX - 16U For seal() the enc_len would need to be > SIZE_MAX - 64U
CVE-2026-2588 Crítica · 9.1 CWE-190 22/02/2026
Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems
Crypt::NaCl::Sodium versions through 2.001 for Perl has an integer overflow flaw on 32-bit systems. Sodium.xs casts a STRLEN (size_t) to unsigned long long when passing a length pointer to libsodium functions. On 32-bit systems size_t is typically 32-bits while an unsigned long long is at least 64-bits.