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.
References
Link | Resource |
---|---|
https://support.keyfactor.com/s/detail/a6x1Q000000CwC5QAK | Vendor Advisory |
https://www.primekey.com/products/ejbca-enterprise/ | Product Vendor Advisory |
https://support.keyfactor.com/s/detail/a6x1Q000000CwC5QAK | Vendor Advisory |
https://www.primekey.com/products/ejbca-enterprise/ | Product Vendor Advisory |
Configurations
History
21 Nov 2024, 07:10
Type | Values Removed | Values Added |
---|---|---|
References | () https://support.keyfactor.com/s/detail/a6x1Q000000CwC5QAK - Vendor Advisory | |
References | () https://www.primekey.com/products/ejbca-enterprise/ - Product, Vendor Advisory |
Information
Published : 2022-09-14 03:15
Updated : 2024-11-21 07:10
NVD link : CVE-2022-34831
Mitre link : CVE-2022-34831
CVE.ORG link : CVE-2022-34831
JSON object : View
Products Affected
primekey
- ejbca
CWE
CWE-295
Improper Certificate Validation