XWiki Solr script service doesn't take dropped programming right into account
xwiki-platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.xwiki.platform:xwiki-platform-search-solr-api Maven |
|
|
xwiki-platform
| Product | Affected | Fixed in |
|---|---|---|
| org.xwiki.platform:xwiki-platform-search-solr-api Maven |
|
|
XWiki is a generic wiki platform. In versions starting from 4.5.1 to before 15.10.13, from 16.0.0-rc-1 to before 16.4.4, and from 16.5.0-rc-1 to before 16.8.0-rc-1, the Solr script service doesn't take dropped programming rights into account. The Solr script service that is accessible in XWiki's scripting API normally requires programming rights to be called. Due to using the wrong API for checking rights, it doesn't take the fact into account that programming rights might have been dropped by calling `$xcontext.dropPermissions()`. If some code relies on this for the safety of executing Velocity code with the wrong author context, this could allow a user with script rights to either cause a high load by indexing documents or to temporarily remove documents from the search index. This issue has been patched in versions 15.10.13, 16.4.4, and 16.8.0-rc-1.
From the CVE record · GitHub_M
The Solr script service does not account for programming rights dropped through `$xcontext.dropPermissions()`. If code relies on that call to safely execute Velocity code with the wrong author context, a user with script rights could cause high load by indexing documents or temporarily remove documents from the search index.
Check deployments using Maven package org.xwiki.platform:xwiki-platform-search-solr-api in versions >=4.5.1 <15.10.13, >=16.0.0-rc-1 <16.4.4, or >=16.5.0-rc-1 <16.8.0-rc-1.