CVE-2022-39387

XWiki OIDC Authenticator vulnerable to bypassing OpenID login by providing a custom provider

Workarounds

There is no workaround, an upgrade of the authenticator is required.

References

https://jira.xwiki.org/browse/OIDC-118

For more information

If you have any questions or comments about this advisory:

• Open an issue in Jira XWiki
• Email us at our security mailing list

Even if a wiki has an OpenID provider configured through its xwiki.properties, it is possible to provide a third party provider by providing its details through request parameters. One can then bypass the XWiki authentication altogether by specifying its own provider through the oidc.endpoint.* request parameters (or by using an XWiki-based OpenID provider with oidc.xwikiprovider.

With the same approach, one could also provide a specific group mapping through oidc.groups.mapping that would make his user automatically part of the XWikiAdminGroup

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-2022-39387 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no 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 (1.29.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Patched in version 1.29.1.

1. What is CVE-2022-39387? CVE-2022-39387 is a critical-severity improper authentication vulnerability in org.xwiki.contrib.oidc:oidc-authenticator (maven), affecting versions < 1.29.1. It is fixed in 1.29.1. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is CVE-2022-39387? CVE-2022-39387 has a CVSS score of 9.1 (Critical). 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.
3. Which versions of org.xwiki.contrib.oidc:oidc-authenticator are affected by CVE-2022-39387? org.xwiki.contrib.oidc:oidc-authenticator (maven) versions < 1.29.1 is affected.
4. Is there a fix for CVE-2022-39387? Yes. CVE-2022-39387 is fixed in 1.29.1. Upgrade to this version or later.
5. Is CVE-2022-39387 exploitable, and should I be worried? Whether CVE-2022-39387 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
6. What actually determines whether CVE-2022-39387 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.
7. How do I fix CVE-2022-39387? Upgrade org.xwiki.contrib.oidc:oidc-authenticator to 1.29.1 or later.

Other vulnerabilities in org.xwiki.contrib.oidc:oidc-authenticator