Vulnerability 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.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Primekey | Ejbca | < 7.9.0 |
Related Weaknesses (CWE)
References
- https://support.keyfactor.com/s/detail/a6x1Q000000CwC5QAKVendor Advisory
- https://www.primekey.com/products/ejbca-enterprise/ProductVendor Advisory
- https://support.keyfactor.com/s/detail/a6x1Q000000CwC5QAKVendor Advisory
- https://www.primekey.com/products/ejbca-enterprise/ProductVendor Advisory
FAQ
What is CVE-2022-34831?
CVE-2022-34831 is a vulnerability with a CVSS score of 9.8 (CRITICAL). 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 finalizat...
How severe is CVE-2022-34831?
CVE-2022-34831 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2022-34831?
Check the references section above for vendor advisories and patch information. Affected products include: Primekey Ejbca.