Dogtag PKI vulnerabilities

In Dogtag PKI's ACME responder, web.xml security constraints use exact URL pattern matching for admin-only enable/disable endpoints. Appending a trailing slash bypasses Tomcat authentication while RESTEasy still routes the request, allowing unauthorized toggling of ACME service state including persistent denial of service.

A flaw was found in Dogtag PKI (pki-core). The CMCAuthForEST authentication plugin fails open when an EST fullcmc enrollment request is submitted via BasicAuth without an end-user TLS client certificate. The SSL_CLIENT_CERT session attribute retains the EST subsystem's agent certificate, causing downstream authorization checks to treat the request as agent-privileged. An authenticated EST user can obtain CA-signed certificates with arbitrary subject names.

A vulnerability in Dogtag PKI, as used by FreeIPA's certificate authority component. The certificate profile import functionality does not fully validate uploaded profile content beyond the profile ID. An authenticated user with CA Administrator privileges can exploit Dogtag's ExternalProcessConstraint mechanism to execute arbitrary commands with attacker-controlled environment variables, achieving code execution as the pkiuser account.

A flaw was found in Dogtag PKI's ACME responder where the HTTP-01 challenge validator accepts IP address literals as dns identifiers and follows HTTP redirects without validating that the target is a public address. An unauthenticated ACME account holder can exploit this to perform SSRF, making the Dogtag server send HTTP GET requests to internal network services. With the InMemory database backend, the response body of internal targets is disclosed to the attacker through the ACME challenge error.