1390 287
Advisory Published


First published: Fri Sep 15 2023(Updated: )

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: > > https://github.com/eclipse/jetty.project/blob/jetty-10.0.14/jetty-openid/src/main/java/org/eclipse/jetty/security/openid/OpenIdAuthenticator.java#L505 > > 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

Affected SoftwareAffected VersionHow to fix

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the vulnerability ID of this Jetty OpenIdAuthenticator vulnerability?

    The vulnerability ID is GHSA-pwh8-58vv-vw48.

  • What is the severity of the GHSA-pwh8-58vv-vw48 vulnerability?

    The severity of the GHSA-pwh8-58vv-vw48 vulnerability is low with a severity value of 3.5.

  • How does the GHSA-pwh8-58vv-vw48 vulnerability affect the Jetty OpenIdAuthenticator?

    If a Jetty OpenIdAuthenticator uses the optional nested LoginService and that LoginService decides to revoke an already authenticated user, the current request will still treat the user as authenticated, but subsequent requests will not.

  • Which versions of Jetty OpenIdAuthenticator are affected by the GHSA-pwh8-58vv-vw48 vulnerability?

    Versions of Jetty OpenIdAuthenticator before 11.0.16, 10.0.16, and 9.4.52 are affected by the GHSA-pwh8-58vv-vw48 vulnerability.

  • How can I fix the GHSA-pwh8-58vv-vw48 vulnerability in Jetty OpenIdAuthenticator?

    To fix the GHSA-pwh8-58vv-vw48 vulnerability in Jetty OpenIdAuthenticator, you need to update to version 11.0.16, 10.0.16, or 9.4.52 or later.


SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203