REDHAT-BUG-2357738: High severity Openid mod_auth_openidc vulnerability
modauthopenidc is an OpenID Certified authentication and authorization module for the Apache 2.x HTTP server that implements the OpenID Connect Relying Party functionality. Prior to 2.4.16.11, a bug in a modauthopenidc results in disclosure of protected content to unauthenticated users. The conditions for disclosure are an OIDCProviderAuthRequestMethod POST, a valid account, and there mustn't be any application-level gateway (or load balancer etc) protecting the server. When you request a protected resource, the response includes the HTTP status, the HTTP headers, the intended response (the self-submitting form), and the protected resource (with no headers). This is an example of a request for a protected resource, including all the data returned. In the case where modauthopenidc returns a form, it has to return OK from checkuserid so as not to go down the error path in httpd. This means httpd will try to issue the protected resource. oidccontenthandler is called early, which has the opportunity to prevent the normal output being issued by httpd. oidccontenthandler has a number of checks for when it intervenes, but it doesn't check for this case, so the handler returns DECLINED. Consequently, httpd appends the protected content to the response. The issue has been patched in modauthopenidc versions >= 2.4.16.11.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2357738?
REDHAT-BUG-2357738 is classified with a high severity due to the potential for unauthorized content disclosure.
How do I fix REDHAT-BUG-2357738?
To fix REDHAT-BUG-2357738, upgrade mod_auth_openidc to version 2.4.16.11 or later.
What are the consequences of not addressing REDHAT-BUG-2357738?
Failure to address REDHAT-BUG-2357738 may allow unauthenticated users to access protected content.
Which versions of mod_auth_openidc are affected by REDHAT-BUG-2357738?
Versions of mod_auth_openidc prior to 2.4.16.11 are affected by REDHAT-BUG-2357738.
Is there a workaround for REDHAT-BUG-2357738 until I can upgrade?
Currently, no official workarounds exist for REDHAT-BUG-2357738, and upgrading is the recommended action.