Ipa: privilege escalation via krbcanonicalname manipulation due to realm-unaware uniqueness enforcement in freeipa ldap datastore
- 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
- 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A privilege escalation flaw was found in FreeIPA. The uniqueness constraint enforced on Kerberos principal name attributes in the 389-ds directory server does not properly account for equivalent representations of the same principal name, allowing a user with sufficient LDAP write privileges to create a service principal that impersonates an existing privileged one. This can lead to unauthorized acquisition of Kerberos service tickets for sensitive services, potentially resulting in full domain compromise.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- ipa
Version range not reported
- ipa
Version range not reported
- idm:client
Version range not reported
- idm:DL1
Version range not reported
- idm:client
Version range not reported
- idm:DL1
Version range not reported
- idm:client
Version range not reported
- idm:DL1
Version range not reported
- idm:client
Version range not reported
- idm:DL1
Version range not reported
- idm:client
Version range not reported
- idm:DL1
Version range not reported
- ipa
Version range not reported
- ipa
Version range not reported
- ipa
Version range not reported
- ipa
Version range not reported
- ipa
Version range not reported
- ipa
Version range not reported
- ipa
Version range not reported