Approved changes feed: RSS · Atom
cpe:2.3:a:primekey:ejbca:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Primekey (c9b1cd0f-61a3-5ab5-9630-786c7c76954f) |
|---|---|
| Product | Ejbca (2e4f2945-2a9a-5ff2-a876-6d728695f574) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:docker/bitnami/ejbca |
purl2cpe | 2026-06-01 10:12:22.948589 |
pkg:github/rgorosito/ejbca |
purl2cpe | 2026-06-01 10:12:22.948593 |
pkg:sourceforge/ejbca |
purl2cpe | 2026-06-01 10:12:22.948595 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-34831 |
vulnerable | 2026-06-08 05:46:03.620217 |
Details available
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.
Published: 2022-09-14T02:58:52.000Z
Updated: 2024-08-03T09:22:10.319Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.