CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2022 · Primekey

CVE-2022-34831
Primekey Ejbca vulnerability

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.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Ejbca. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Primekey Ejbca runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Primekey products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.