CVE-2025-40918

Authen::SASL::Perl::DIGEST_MD5 versions 2.04 through 2.1800 for Perl generates the cnonce insecurely. The cnonce (client nonce) is generated from an MD5 hash of the PID, the epoch time and the built-in rand function. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage. According to RFC 2831, The cnonce-value is an opaque quoted string value provided by the client and used by both client and server to avoid chosen plaintext attacks, and to provide mutual authentication. The security of the implementation depends on a good choice. It is RECOMMENDED that it contain at least 64 bits of entropy.

Authen::SASL::Perl::DIGEST_MD5 versions 2.04 through 2.1800 for Perl generates the cnonce insecurely. The cnonce (client nonce) is generated from an MD5 hash of the PID, the epoch time and the built-in rand function. The PID will come from a small set of numbers, and the epoch time may be guessed, if it is not leaked from the HTTP Date header. The built-in rand function is unsuitable for cryptographic usage. According to RFC 2831, The cnonce-value is an opaque quoted string value provided by the client and used by both client and server to avoid chosen plaintext attacks, and to provide mutual authentication. The security of the implementation depends on a good choice. It is RECOMMENDED that it contain at least 64 bits of entropy.

Authen::SASL::Perl::DIGEST_MD5, versiones 2.04 a 2.1800 para Perl, genera el cnonce de forma insegura. El cnonce (nonce del cliente) se genera a partir de un hash MD5 del PID, la fecha de la época y la función rand integrada. El PID se obtendrá de un pequeño conjunto de números, y la fecha de la época puede ser inferida si no se filtra del encabezado HTTP Date. La función rand integrada no es adecuada para uso criptográfico. Según la RFC 2831, el valor cnonce es una cadena opaca entre comillas proporcionada por el cliente y utilizada tanto por el cliente como por el servidor para evitar ataques de texto plano y proporcionar autenticación mutua. La seguridad de la implementación depende de una buena elección. Se recomienda que contenga al menos 64 bits de entropía.