CyberRota Analysis
AI-GeneratedLemonldap::NG::Portal versions prior to 2.21.6 and 2.23.4 are vulnerable to unauthenticated OAuth2 token introspection due to a flaw in the checkEndPointAuthenticationCredentials function, which fails to validate the client secret for public Relying Parties. This allows attackers with access tokens and knowledge of a public client_id to confirm token validity and retrieve sensitive metadata, potentially compromising user identifiers across different Relying Parties. Organizations using affected versions should prioritize remediation to protect against unauthorized access and data exposure.
Original NVD Description
Lemonldap::NG::Portal versions from 2.20.0 before 2.21.6, from 2.22.0 before 2.23.4 for Perl allow unauthenticated OAuth2 token introspection because checkEndPointAuthenticationCredentials does not verify the client secret of a public Relying Party. checkEndPointAuthenticationCredentials() skips the secret comparison for a Relying Party marked public and still returns the authentication method deduced from the request, client_secret_basic or client_secret_post. introspection() rejects a caller only when that method is missing or none, so a request carrying a public client_id and an arbitrary or empty secret passes the endpoint's authentication check. An attacker who holds an access token and knows the client_id of any public Relying Party can confirm the token is active and read its metadata, including scope, audience, expiry and the sub claim. The sub claim is computed with the calling Relying Party's user identifier attribute, so an attacker can translate a user identifier from one Relying Party to another, defeating per-client and pseudonymous identifiers.