# CVE-2024-58135: Weak cryptography in Mojolicious

> Weak HMAC secrets in Mojolicious allow attackers to brute force session keys, potentially leading to account takeover or security bypass.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2025
- **Updated:** 5 Jun 2026
- **Also known as:** AZL-61741, AZL-61822, DEBIAN-CVE-2024-58135, GHSA-3r5v-gmfp-3mh9, UBUNTU-CVE-2024-58135

## What is CVE-2024-58135?

CVE-2024-58135 is a medium-severity vulnerability in SRI Mojolicious, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2024-58135?

It affects 1 product.


Products: Mojolicious Mojolicious.

## How do I fix CVE-2024-58135?

No fix has been published for CVE-2024-58135 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-58135 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-58135 exists.

## Other vulnerabilities in SRI Mojolicious

- [CVE-2009-5074](https://insights.sbomify.com/CVE-2009-5074/): Other in n/a (critical 10.0)
- [CVE-2010-4802](https://insights.sbomify.com/CVE-2010-4802/): Other in n/a (critical 10.0)
- [CVE-2010-4803](https://insights.sbomify.com/CVE-2010-4803/): Weak cryptography in n/a (critical 10.0)
- [CVE-2024-58134](https://insights.sbomify.com/CVE-2024-58134/): Hardcoded credentials in Mojolicious (high 8.1)
- [CVE-2011-1589](https://insights.sbomify.com/CVE-2011-1589/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-58135 and fix it if it is affected.

What it is: CVE-2024-58135 is a medium-severity vulnerability in SRI Mojolicious, published on 3 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-58135 exists.

Affected product: SRI Mojolicious. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-58135/ (Markdown: https://insights.sbomify.com/CVE-2024-58135/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-58135
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-58135
- OSV: https://osv.dev/vulnerability/CVE-2024-58135

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-58135/
Summaries are generated and may contain mistakes; the official description above is the record.