Ecosyste.ms: Advisories
An open API service providing security vulnerability metadata for many open source software ecosystems.
Security Advisories: GSA_kwCzR0hTQS1wd2g4LTU4dnYtdnc0OM4AA15T
Jetty's OpenId Revoked authentication allows one request
If a Jetty OpenIdAuthenticator
uses the optional nested LoginService
, and that LoginService
decides to revoke an already authenticated user, then the current request will still treat the user as authenticated. The authentication is then cleared from the session and subsequent requests will not be treated as authenticated.
So a request on a previously authenticated session could be allowed to bypass authentication after it had been rejected by the LoginService
.
Impact
This impacts usages of the jetty-openid which have configured a nested LoginService
and where that LoginService
will is capable of rejecting previously authenticated users.
Original Report
working on a custom OpenIdAuthenticator, I discovered the following:
In the case where the LoginService does return that the authentication has been revoked (from the validate() call on line 463), the OpenIdAuthenticator removes the authentication from the session; however the current request still proceeds as if authenticated, since it falls through to "return authentication" on line 505.
This is fixed by moving the line 505 (and associated debug log) inside the else block that ends on line 502, instead of outside it. Then the revocation case will run through to line 517 and will trigger a new OpenId authentication which I think is correct.
I think this revocation can only occur if you do attach a separate LoginService to the OpenIdLoginService, but in that case the revoked authentication will still let the next request through (and possibly more than one if they are very close to simultaneous).
Technically I think this is a security vulnerability, if a very minor one, so I'm sending this off-list.
Patched Versions
Fixed in Jetty Versions:
- 9.4.52 - fixed in PR https://github.com/eclipse/jetty.project/pull/9660
- 10.0.16 - fixed in PR https://github.com/eclipse/jetty.project/pull/9528
- 11.0.16 - fixed in PR https://github.com/eclipse/jetty.project/pull/9528
- 12.0.0 - not impacted (already has fix)
Workaround
Upgrade your version of Jetty.
References
- https://github.com/eclipse/jetty.project/pull/9528
- https://github.com/eclipse/jetty.project/pull/9660
JSON: https://advisories.ecosyste.ms/api/v1/advisories/GSA_kwCzR0hTQS1wd2g4LTU4dnYtdnc0OM4AA15T
Source: GitHub Advisory Database
Origin: Unspecified
Severity: Low
Classification: General
Published: about 1 year ago
Updated: 2 months ago
CVSS Score: 3.5
CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N
Identifiers: GHSA-pwh8-58vv-vw48, CVE-2023-41900
References:
- https://github.com/eclipse/jetty.project/security/advisories/GHSA-pwh8-58vv-vw48
- https://github.com/eclipse/jetty.project/pull/9528
- https://github.com/eclipse/jetty.project/pull/9660
- https://nvd.nist.gov/vuln/detail/CVE-2023-41900
- https://www.debian.org/security/2023/dsa-5507
- https://security.netapp.com/advisory/ntap-20231110-0004
- https://github.com/advisories/GHSA-pwh8-58vv-vw48
Blast Radius: 5.4
Affected Packages
maven:org.eclipse.jetty:jetty-openid
Dependent packages: 53Dependent repositories: 36
Downloads:
Affected Version Ranges: >= 9.4.21, <= 9.4.51, >= 11.0.0, <= 11.0.15, >= 10.0.0, <= 10.0.15
Fixed in: 9.4.52.v20230823, 11.0.16, 10.0.16
All affected versions: 10.0.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.0.5, 10.0.6, 10.0.7, 10.0.8, 10.0.9, 10.0.10, 10.0.11, 10.0.12, 10.0.13, 10.0.14, 10.0.15, 11.0.0, 11.0.1, 11.0.2, 11.0.3, 11.0.4, 11.0.5, 11.0.6, 11.0.7, 11.0.8, 11.0.9, 11.0.10, 11.0.11, 11.0.12, 11.0.13, 11.0.14, 11.0.15
All unaffected versions: 10.0.16, 10.0.17, 10.0.18, 10.0.19, 10.0.20, 10.0.21, 10.0.22, 10.0.23, 10.0.24, 11.0.16, 11.0.17, 11.0.18, 11.0.19, 11.0.20, 11.0.21, 11.0.22, 11.0.23, 11.0.24, 12.0.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, 12.0.5, 12.0.6, 12.0.7, 12.0.8, 12.0.9, 12.0.10, 12.0.11, 12.0.12, 12.0.13, 12.0.14, 12.0.15