Name | CVE-2019-15941 |
Description | OpenID Connect Issuer in LemonLDAP::NG 2.x through 2.0.5 may allow an attacker to bypass access control rules via a crafted OpenID Connect authorization request. To be vulnerable, there must exist an OIDC Relaying party within the LemonLDAP configuration with weaker access control rules than the target RP, and no filtering on redirection URIs. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
References | DSA-4533-1 |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
lemonldap-ng (PTS) | jessie, jessie (lts) | 1.3.3-1+deb8u2 | fixed |
| stretch (security), stretch (lts), stretch | 1.9.7-3+deb9u4 | vulnerable |
| buster, buster (lts) | 2.0.2+ds-7+deb10u11 | fixed |
| buster (security) | 2.0.2+ds-7+deb10u10 | fixed |
| bullseye | 2.0.11+ds-4+deb11u5 | fixed |
| bullseye (security) | 2.0.11+ds-4+deb11u6 | fixed |
| bookworm | 2.16.1+ds-deb12u3 | fixed |
| sid, trixie | 2.20.1+ds-1 | fixed |
The information below is based on the following data on fixed versions.
Notes
[stretch] - lemonldap-ng <ignored> (Restrictions on OIDC federation added in 2.0)
[jessie] - lemonldap-ng <not-affected> (Vulnerable code introduced later)
Vulnerability exists pre-2.0 versions, but as restrictions on OIDC federation
were added only in 2.0 the vulnerability has no effect. The vulnerability
itself exists only with versions >= 1.9.0 (as there is no OIDC before)