Executive brief
OpenAM, an open-source identity and access management platform, is vulnerable to a security flaw in its user and group query interfaces. An attacker with a valid session token can send specially crafted requests to extract sensitive information from the underlying user directory. This could lead to the exposure of user lists or other directory data, potentially compromising the privacy of the identity system.
Technical details
An LDAP injection vulnerability exists in OpenAM's CREST REST API layer, specifically within the `IdentityResourceV1.queryCollection()` method. The `_queryId` HTTP parameter is passed to a `CrestQuery` object with the `escapeQueryId` flag explicitly set to `false`, bypassing previous security fixes (CVE-2021-29156). This unsanitized input reaches `DJLDAPv3Repo.getFilter()`, where it is concatenated into an LDAP filter string. Authenticated attackers with a valid SSO token can exploit this to inject arbitrary LDAP metacharacters via the `/json/{realm}/users` or `/json/{realm}/groups` endpoints. This enables user enumeration and blind LDAP injection against the backend directory. The issue is fixed in version 16.1.1.
Affected products
- Open Identity Platform OpenAM <= 16.0.6
Timeline
- 2026-06-20: disclosed
- 2026-06-22: advisory: GitHub Advisory published
- 2026-06-22: patched: Version 16.1.1 released