# CVE-2022-34831: Business logic in n/a

> Attackers can bypass ACME validation to issue certificates with unverified DNS names, undermining PKI trust integrity.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-ejbca-2022-34831, GHSA-w496-q2jp-3qx5

## What is CVE-2022-34831?

CVE-2022-34831 is a critical vulnerability in n/a, published on 14 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Keyfactor PrimeKey EJBCA before 7.9.0, related to possible inconsistencies in DNS identifiers submitted in an ACME order and the corresponding CSR submitted during finalization. During the ACME enrollment process, an order is submitted containing an identifier for one or multiple dnsNames. These are validated properly in the ACME challenge. However, if the validation passes, a non-compliant client can include additional dnsNames the CSR sent to the finalize endpoint, resulting in EJBCA issuing a certificate including the identifiers that were not validated. This occurs even if the certificate profile is configured to not allow a DN override by the CSR.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-34831?

1 open source package ship an affected version, including ejbca. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ejbca` | Bitnami | All versions | 7.9.0 |

Products: Primekey Ejbca.

## How do I fix CVE-2022-34831?

Upgrade ejbca to 7.9.0 or later.

## Is CVE-2022-34831 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11630](https://insights.sbomify.com/CVE-2020-11630/): Deserialization in n/a (critical 9.8)
- [CVE-2020-11627](https://insights.sbomify.com/CVE-2020-11627/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-25276](https://insights.sbomify.com/CVE-2020-25276/): Security feature bypass in n/a (high 7.3)
- [CVE-2020-11629](https://insights.sbomify.com/CVE-2020-11629/): File upload in n/a (high 7.2)
- [CVE-2020-11631](https://insights.sbomify.com/CVE-2020-11631/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34831 and fix it if it is affected.

What it is: CVE-2022-34831 is a critical vulnerability in n/a, published on 14 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34831 in the wild and no public exploit code.

Affected packages and fixed versions:
- ejbca (Bitnami): affected all versions; fixed in 7.9.0

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

## Sources

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

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