Bug 2540880 (CVE-2026-92288) - CVE-2026-92288 lemonldap-ng: lemonldap-ng: Information disclosure via unauthenticated OAuth 2.0 token introspection
Summary: CVE-2026-92288 lemonldap-ng: lemonldap-ng: Information disclosure via unauthe...
Keywords:
Status: NEW
Alias: CVE-2026-92288
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2540974 2540975
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-25 01:01 UTC by OSIDB Bzimport
Modified: 2026-09-25 07:34 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-25 01:01:19 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.