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 server-side request forgery (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.

An unauthenticated client can query the Security Domain hosts inventory via GET /ca/rest/securityDomain/hosts and receive a structured response enumerating internal PKI/CA hosts and roles (security domain topology and participating subsystems), without requiring a principal, client certificate, or session.

Description An unauthenticated client can query the Security Domain hosts inventory via GET /ca/rest/securityDomain/hosts and receive a structured response enumerating internal PKI/CA hosts and roles (security domain topology / participating subsystems / hostnames). This is information disclosure at an authentication boundary: inventory/relationship metadata is exposed without requiring a principal, client cert, or session. An unauthenticated adversary with access to the network could enumerate PKI host/subsystem topology, target high-value Dogtag endpoints, or craft follow-on attacks (SSRF/pivots/phishing) using real internal names. Recommendations There is no reason to share the foreman version in the response and should be masked.

An Apache-proxied Dogtag CA REST endpoint exposed by IdM (POST /ca/rest/certrequests) returns HTTP 500 with internal Java stack traces for unauthenticated malformed requests. The same unauthenticated error path emits large multi-line stack traces into the CA debug log, creating a log-amplification resource exhaustion vector (disk growth and I/O contention) without requiring authentication.

A flaw was found in dogtag-pki and pki-core. The token authentication scheme can be bypassed with a LDAP injection. By passing the query string parameter sessionID=, an attacker can authenticate with an existing session saved in the LDAP directory server, which may lead to escalation of privilege.

The token authentication scheme in Dogtag CA can be bypassed with a Ldap injection. By passing the query string parameter sessionID=, an attacker can authenticate with the existing session saved in Ldap directory server.

It was discovered that the Red Hat Certificate System's / Dogtag Certificate System's Certificate Manager did not properly check certificate revocation requests. An agent permitted to perform revocations of end entity certificates via Certificate System's web interface could use this flaw to revoke the Certificate Authority (CA) certificate.

The issue was originally reported via bug #832212.

Patch applied to address this issue: https://fedorahosted.org/pki/changeset/2430