CVE-2022-39387
published 2022-11-04CVE-2022-39387: XWiki OIDC has various tools to manipulate OpenID Connect protocol in XWiki. Prior to version 1.29.1, even if a wiki has an OpenID provider configured through…
PriorityP343high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
0.90%
55.0th percentile
XWiki OIDC has various tools to manipulate OpenID Connect protocol in XWiki. Prior to version 1.29.1, even if a wiki has an OpenID provider configured through its xwiki.properties, it is possible to provide a third party provider 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. This issue has been patched, please upgrade to 1.29.1. There is no workaround, an upgrade of the authenticator is required.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| xwiki-contrib | oidc | < 1.29.1 | 1.29.1 |
| xwiki | openid_connect | < 1.29.1 | 1.29.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
XWiki OIDC Authenticator vulnerable to bypassing OpenID login by providing a custom provider
osv·2022-11-04
CVE-2022-39387 [CRITICAL] XWiki OIDC Authenticator vulnerable to bypassing OpenID login by providing a custom provider
XWiki OIDC Authenticator vulnerable to bypassing OpenID login by providing a custom provider
### Impact
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
### Patches
Patched in version 1.29.1.
### Workarounds
There is no workaround, an upgrade of the authenticator is required.
### Reference
GHSA
XWiki OIDC Authenticator vulnerable to bypassing OpenID login by providing a custom provider
ghsa·2022-11-04
CVE-2022-39387 [CRITICAL] CWE-287 XWiki OIDC Authenticator vulnerable to bypassing OpenID login by providing a custom provider
XWiki OIDC Authenticator vulnerable to bypassing OpenID login by providing a custom provider
### Impact
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
### Patches
Patched in version 1.29.1.
### Workarounds
There is no workaround, an upgrade of the authenticator is required.
### Reference
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/xwiki-contrib/oidc/commit/0247af1417925b9734ab106ad7cd934ee870ac89https://github.com/xwiki-contrib/oidc/security/advisories/GHSA-m7gv-v8xx-v47whttps://jira.xwiki.org/browse/OIDC-118https://github.com/xwiki-contrib/oidc/commit/0247af1417925b9734ab106ad7cd934ee870ac89https://github.com/xwiki-contrib/oidc/security/advisories/GHSA-m7gv-v8xx-v47whttps://jira.xwiki.org/browse/OIDC-118
2022-11-04
Published