# CVE-2024-13454: Weak cryptography in Easy-RSA

> A local attacker can more easily brute-force the private CA key due to weak encryption algorithms in Easy-RSA when used with OpenSSL 3.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jan 2025
- **Updated:** 21 Jan 2025
- **Also known as:** DEBIAN-CVE-2024-13454, GHSA-rc52-2qp6-xmff, UBUNTU-CVE-2024-13454

## What is CVE-2024-13454?

CVE-2024-13454 is a medium-severity vulnerability in OpenVPN Easy-RSA, published on 20 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Weak encryption algorithm in Easy-RSA version 3.0.5 through 3.1.7 allows a local attacker to more easily bruteforce the private CA key when created using OpenSSL 3

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 1 product.


Products: Openvpn Easy-Rsa.

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

Upgrade to a fixed version.

## Is CVE-2024-13454 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-13454 is a medium-severity vulnerability in OpenVPN Easy-RSA, published on 20 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13454 in the wild and no public exploit code.

Affected product: OpenVPN Easy-RSA. 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-13454/ (Markdown: https://insights.sbomify.com/CVE-2024-13454/index.md)
```

## Sources

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

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