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.
Security readout for executives and security teams
Plain-English summary
CVE-2023-4727 is an authentication bypass in Dogtag PKI / Red Hat pki-core certificate authority components. A malformed session identifier can abuse LDAP session lookup and authenticate as an existing saved session. For organizations using Red Hat Certificate System or Dogtag-based CA services, this could affect certificate authority trust operations and privileges.
Executive priority
Prioritize remediation for certificate authority infrastructure because compromise can affect identity, trust, and certificate issuance workflows. Treat as high priority for exposed or shared PKI services, while noting there is no sourced evidence of active exploitation in this bundle.
Technical view
The flaw is in the token authentication scheme for dogtag-pki / pki-core. LDAP injection in session lookup can allow authentication using an existing session stored in LDAP. Red Hat rates it High with CVSS 3.1 score 7.5, high complexity, no privileges required, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is likely where affected Red Hat pki-core or redhat-pki:10 packages run CA services on listed RHEL 7, 8, 9, EUS, AUS, TUS, or E4S streams. Keycloak is marked unaffected in the provided data. RHEL 6 status is unknown and needs vendor confirmation.
Exploitation context
The bundle does not show CISA KEV listing or cited active exploitation. Exploitation appears to require access to the vulnerable CA service and an existing saved LDAP session. CVSS lists adjacent attack vector and high attack complexity, but no prior authentication or user interaction.
Researcher notes
Primary issue maps to CWE-305: authentication bypass by primary weakness. Public references include Red Hat advisories, Red Hat CVE entry, Bugzilla, GitHub advisory, and Dogtag PKI commits. Evidence is incomplete for RHEL 6 status and for any real-world exploitation.
Mitigation direction
Apply the relevant Red Hat security advisory updates for your RHEL or Certificate System stream.
Update affected pki-core or redhat-pki:10 packages according to Red Hat guidance.
Restrict network access to CA and PKI administrative interfaces where feasible.
For RHEL 6 or unclear deployments, request Red Hat support guidance.
Validation and detection
Inventory systems running dogtag-pki, pki-core, or Red Hat Certificate System.
Compare installed package versions against the affected versions in Red Hat advisories.
Confirm the applicable RHSA update is installed for each supported stream.
Review CA authentication logs for unusual session identifier handling or failed token authentication events.
Do not classify Keycloak as affected based only on this bundle.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-305: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
5Timeline events
2ADP providers
15Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-305 · source CWE mapping
Authentication Bypass by Primary Weakness
Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.