Описание
Mojolicious versions from 7.28 through 9.45 for Perl will generate weak HMAC session cookie secrets via "mojo generate app" by default. When creating a default app skeleton with the "mojo generate app" tool, a weak secret is written to the application's configuration file using the insecure rand() function, and used for authenticating and protecting the integrity of the application's sessions. This may allow an attacker to brute force the application's session keys. Release 9.46 fixes the issue by providing high quality randomness, even in absence of CryptX. Users should be aware that the update does not replace previously generated weak secrets. A secret generated with the previous version MUST be replaced to ensure the updated version is using a strong secret.
Пакеты
| Пакет | Статус | Версия исправления | Релиз | Тип |
|---|---|---|---|---|
| libmojolicious-perl | unfixed | package | ||
| libmojolicious-perl | no-dsa | trixie | package | |
| libmojolicious-perl | no-dsa | bookworm | package | |
| libmojolicious-perl | postponed | bullseye | package |
Примечания
https://lists.security.metacpan.org/cve-announce/msg/29241187/
https://github.com/mojolicious/mojo/commit/c82071556c569a251152892c8cc2fd0ad5a4be54 (v9.39)
The problem does not occur if the user has configured a cryptographically
secure HMAC session secret, and upstream expects users to already be doing
that for production deployments. The fix automatically generates a secure
session secret. It requires libcryptx-perl >=0.080, but they say this is
only because that is the only release they tested. I.e., it is likely that
the fix works fine with older CryptX: https://github.com/mojolicious/mojo/discussions/2255
As per upstream mojolicious/v9.39 will still be considered vulnerable to the
CVE since the CryptX is not a required dependency.
Связанные уязвимости
Mojolicious versions from 7.28 through 9.45 for Perl will generate weak HMAC session cookie secrets via "mojo generate app" by default. When creating a default app skeleton with the "mojo generate app" tool, a weak secret is written to the application's configuration file using the insecure rand() function, and used for authenticating and protecting the integrity of the application's sessions. This may allow an attacker to brute force the application's session keys. Release 9.46 fixes the issue by providing high quality randomness, even in absence of CryptX. Users should be aware that the update does not replace previously generated weak secrets. A secret generated with the previous version MUST be replaced to ensure the updated version is using a strong secret.
Mojolicious versions from 7.28 through 9.45 for Perl will generate weak HMAC session cookie secrets via "mojo generate app" by default. When creating a default app skeleton with the "mojo generate app" tool, a weak secret is written to the application's configuration file using the insecure rand() function, and used for authenticating and protecting the integrity of the application's sessions. This may allow an attacker to brute force the application's session keys. Release 9.46 fixes the issue by providing high quality randomness, even in absence of CryptX. Users should be aware that the update does not replace previously generated weak secrets. A secret generated with the previous version MUST be replaced to ensure the updated version is using a strong secret.
Mojolicious versions from 7.28 through 9.39 for Perl may generate weak HMAC session secrets. When creating a default app with the "mojo generate app" tool, a weak secret is written to the application's configuration file using the insecure rand() function, and used for authenticating and protecting the integrity of the application's sessions. This may allow an attacker to brute force the application's session keys.