Where
-Infinity
0
Severity
7.5
EPSS
0.03%
Integer Overflow, Buffer Overflow
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Crypt::Sodium::XS versions through 0.001000 for Perl has potential integer overflows.

Combined aead encryption, combined signature creation, and bin2hex functions do not check that output size will be less than SIZEMAX, which could lead to integer wraparound causing an undersized output buffer. This can cause a crash in bin2hex and encryption algorithms other than aes256gcm. For aes256gcm encryption and signatures, an undersized buffer could lead to buffer overflow.

Encountering this issue is unlikely as the message length would need to be very large.

For bin2hex the input size would have to be > SIZEMAX / 2 For aegis encryption the input size would need to be > SIZEMAX - 32U For other encryption the input size would need to be > SIZEMAX - 16U For signatures the input size would need to be > SIZEMAX - 64U

Remedy

Upgrade to version 0.001001
First published (updated )
Severity
9.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Crypt::Sodium::XS module versions prior to 0.000042, for Perl, include a vulnerable version of libsodium

1 / 2
Source: Microsoft

Remedy

Upgrade to version 0.000042 or later
First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203