# CVE-2024-36066: Weak cryptography in n/a

> The EJBCA CMP CLI client uses insufficient salt length, weakening password-based MAC and facilitating man-in-the-middle attacks.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/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:** 12 Sep 2024
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-xmrg-69jq-mfv5

## What is CVE-2024-36066?

CVE-2024-36066 is a low-severity vulnerability in n/a, published on 12 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The CMP CLI client in KeyFactor EJBCA before 8.3.1 has only 6 octets of salt, and is thus not compliant with the security requirements of RFC 4211, and might make man-in-the-middle attacks easier. CMP includes password-based MAC as one of the options for message integrity and authentication (the other option is certificate-based). RFC 4211 section 4.4 requires that password-based MAC parameters use a salt with a random value of at least 8 octets. This helps to inhibit dictionary attacks. Because the standalone CMP client originally was developed as test code, the salt was instead hardcoded and only 6 octets long.

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

It affects 1 product.


Products: Keyfactor Ejbca.

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

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

## Is CVE-2024-36066 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-34196](https://insights.sbomify.com/CVE-2023-34196/): Auth bypass in n/a (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-36066 is a low-severity vulnerability in n/a, published on 12 Sep 2024. 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-36066 in the wild and no public exploit code.

Affected product: n/a. 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-36066/ (Markdown: https://insights.sbomify.com/CVE-2024-36066/index.md)
```

## Sources

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

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