| Name | CVE-2024-58135 |
| Description | Mojolicious versions from 7.28 for Perl will generate weak HMAC sessio ... |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| Debian Bugs | 1104633 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|
| libmojolicious-perl (PTS) | bullseye | 8.71+dfsg-1 | vulnerable |
| bookworm | 9.31+dfsg-1 | vulnerable |
| trixie | 9.39+dfsg-1 | vulnerable |
| forky, sid | 9.42+dfsg-1 | vulnerable |
The information below is based on the following data on fixed versions.
Notes
[trixie] - libmojolicious-perl <no-dsa> (Minor issue)
[bookworm] - libmojolicious-perl <no-dsa> (Minor issue)
[bullseye] - libmojolicious-perl <postponed> (Minor issue)
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.