CVE-2023-4727
Ca: token authentication bypass vulnerability
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 11.5.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- keycloak
fixed in 11.5.1
- redhat-pki:10
Version range not reported
- pki-core
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core:10.6
Version range not reported
- pki-core
Version range not reported
- pki-core
Version range not reported
- pki-core
Version range not reported
- pki-core
Version range not reported