dbcve.org
EjbcaApplication · Primekey

CVE-2022-34831

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-14
Fix available
A fix is available. Upgrade to 7.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Keyfactor PrimeKey EJBCA before 7.9.0, the ACME enrollment process fails to enforce that the DNS identifiers in the CSR match those validated in the ACME order. During finalization, a non-compliant client can submit a CSR containing additional dnsNames that were never validated through ACME challenges, causing EJBCA to issue certificates containing unvalidated identifiers. This bypass occurs even when the certificate profile blocks DN override by CSR.

MitigationUpgrade to EJBCA 7.9.0 or later, which enforces that CSR identifiers must match the validated ACME order identifiers. If immediate upgrade is not possible, consider disabling ACME or restricting ACME to trusted clients only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EjbcaApplication
Affected:< 7.9.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify EJBCA version
    Locate the EJBCA installation and check the version file or admin interface version display. Compare the installed version against the affected range (versions before 7.9.0).
    Affected if Installed version is lower than 7.9.0
  2. Confirm ACME is enabled
    Check the EJBCA configuration or admin interface to determine if the ACME (Automatic Certificate Management Environment) protocol is enabled and accessible.
    Affected if ACME is enabled and accessible to clients
  3. Audit ACME-issued certificates for unvalidated identifiers
    Review certificates issued through ACME enrollment. For each certificate, compare the DNS names in the certificate subject alternative names against the DNS names that were validated in the corresponding ACME order. Look for any dnsNames present in the certificate that were not part of the validated ACME order.
    Affected if Any ACME-issued certificates contain DNS identifiers that were not validated through the ACME challenge process

You are affected if you run EJBCA versions before 7.9.0 with ACME enabled, and any certificates were issued with DNS identifiers that were never validated in the ACME order.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.9.0 or later
Fixed in 7.9.0
Interim mitigation

Upgrade to EJBCA 7.9.0 or later, which enforces that CSR identifiers must match the validated ACME order identifiers. If immediate upgrade is not possible, consider disabling ACME or restricting ACME to trusted clients only.

Recommended fix High confidence

7.9.0

  1. 1. Back up the current EJBCA installation and database before proceeding with the upgrade.
  2. 2. Download EJBCA version 7.9.0 or later from the official Keyfactor/PrimeKey distribution channels.
  3. 3. Review the EJBCA upgrade guide for version 7.9.0 for any specific migration steps or prerequisites.
  4. 4. Stop the EJBCA application server.
  5. 5. Install EJBCA 7.9.0 following the standard installation procedures.
  6. 6. Verify the ACME functionality works correctly by testing certificate enrollment.
  7. 7. Confirm that the certificate issued matches the identifiers in the ACME order and does not include unvalidated dnsNames from the CSR.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ejbca Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-34831 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34831 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data