Summary
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.
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
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.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
CVE-2023-41900 has a CVSS score of 3.5 (Low). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (9.4.52.v20230823, 10.0.16, 11.0.16); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.eclipse.jetty:jetty-openid to 9.4.52.v20230823 or later; org.eclipse.jetty:jetty-openid to 10.0.16 or later; org.eclipse.jetty:jetty-openid to 11.0.16 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2023-41900? CVE-2023-41900 is a low-severity improper authentication vulnerability in org.eclipse.jetty:jetty-openid (maven), affecting versions >= 9.4.21, <= 9.4.51. It is fixed in 9.4.52.v20230823, 10.0.16, 11.0.16. The application does not adequately verify the identity of a user, device, or process before granting access.
- How severe is CVE-2023-41900? CVE-2023-41900 has a CVSS score of 3.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.eclipse.jetty:jetty-openid are affected by CVE-2023-41900? org.eclipse.jetty:jetty-openid (maven) versions >= 9.4.21, <= 9.4.51 is affected.
- Is there a fix for CVE-2023-41900? Yes. CVE-2023-41900 is fixed in 9.4.52.v20230823, 10.0.16, 11.0.16. Upgrade to this version or later.
- Is CVE-2023-41900 exploitable, and should I be worried? Whether CVE-2023-41900 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2023-41900 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2023-41900?
- Upgrade
org.eclipse.jetty:jetty-openidto 9.4.52.v20230823 or later - Upgrade
org.eclipse.jetty:jetty-openidto 10.0.16 or later - Upgrade
org.eclipse.jetty:jetty-openidto 11.0.16 or later
- Upgrade