# CVE-2024-58134: Hardcoded credentials in Mojolicious

> Attackers can forge session cookies using predictable default HMAC secrets to hijack user sessions in Mojolicious applications.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2025
- **Updated:** 20 Oct 2025
- **Also known as:** AZL-61673, AZL-61825, DEBIAN-CVE-2024-58134, GHSA-3g23-7g3r-898j, UBUNTU-CVE-2024-58134

## What is CVE-2024-58134?

CVE-2024-58134 is a high-severity vulnerability in SRI Mojolicious, published on 3 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mojolicious versions from 0.999922 for Perl uses a hard coded string, or the application's class name, as an HMAC session cookie secret by default.

These predictable default secrets can be exploited by an attacker to forge session cookies.  An attacker who knows or guesses the secret could compute valid HMAC signatures for the session cookie, allowing them to tamper with or hijack another user’s session.

Weakness: CWE-331 (Insufficient Entropy), CWE-321 (Use of Hard-coded Cryptographic Key)

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

It affects 1 product.


Products: Mojolicious Mojolicious.

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

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

## Is CVE-2024-58134 being exploited?

There is no known exploitation of CVE-2024-58134 in the wild and no public exploit code.

## 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-58135](https://insights.sbomify.com/CVE-2024-58135/): Weak cryptography in Mojolicious (medium 5.3)
- [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-58134 and fix it if it is affected.

What it is: CVE-2024-58134 is a high-severity vulnerability in SRI Mojolicious, published on 3 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-58134 in the wild and no public exploit code.

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-58134/ (Markdown: https://insights.sbomify.com/CVE-2024-58134/index.md)
```

## Sources

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

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