CVE-2022-41935

Reproduction steps

1. Restrict "view" access to Sandbox.TestPage3 by setting an explicit view right for admins
2. As a user who is not an admin, open <server>/bin/get/XWiki/LiveTableResults?outputSyntax=plain&classname=&collist=doc.title%2Cdoc.location%2Cdoc.content&doc.title=Sandbo&doc.location=Sandbox.TestPage3&doc.content=dummy&limit=0 where <server> is the URL of your XWiki installation.

Expect Result:

No results are displayed as the user doesn't have view rights on Sandbox.TestPage3.

Actual Result:

The result

{
  "reqNo": null,
  "matchingtags": {},
  "tags": [],
  "totalrows": 1,
  "returnedrows": 0,
  "offset": 1,
  "rows": [
    {
      "doc_viewable": false,
      "doc_fullName": "obfuscated"
    }
  ]
}

is displayed.

This reveals that a document Sandbox.TestPage3 exists (we explicitly searched for this name) which has a title containing "Sandbo" and a content containing "dummy". By starting with a single letter and then iteratively extending the match, the full content of the title/content or XObject properties can be discovered. Several tests can be combined in a single request to use binary search to narrow down the actual match from a list of possible characters/words. If the used alphabet is known and smaller than 128 distinct characters, it is possible to discover one character with 7 requests. Alternatively, frequencies of words and word pairs (2-gram frequencies) can be used to first guess whole words and only resort to guessing individual characters if none of the predicted words match, allowing a much faster recovery of the textual content. As it also depends on the content how easy the attack is and how much recovered content would be a "successful" attack, it is hard to quantify how many requests are necessary.

Workarounds

The patch for the document XWiki.LiveTableResultsMacros can be manually applied or a XAR archive of a patched version can be imported, on versions >= 12.10.11, >= 13.9-rc-1, and >= 13.4.4.

References

• https://github.com/xwiki/xwiki-platform/commit/1450b6e3c69ac7df25e5a2571186d1f43402facd#diff-5a739e5865b1f1ad9d79b724791be51b0095a0170cc078911c940478b13b949a
• https://jira.xwiki.org/browse/XWIKI-19999

For more information

If you have any questions or comments about this advisory:

• Open an issue in Jira XWiki.org
• Email us at Security Mailing List

User without the right to view documents can deduce their existence by repeated Livetable queries.

CVE-2022-41935 has a CVSS score of 5.3 (Medium). 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 (13.10.8, 14.4.3, 14.6-rc-1); upgrading removes the vulnerable code path.

Kodem intelligence

The issue has been patched in XWiki 14.6RC1, 13.10.8, and 14.4.3, the response is not properly cleaned up of obfuscated entries.

1. What is CVE-2022-41935? CVE-2022-41935 is a medium-severity security vulnerability in org.xwiki.platform:xwiki-platform-livetable-ui (maven), affecting versions >= 12.10.11, < 13.10.8. It is fixed in 13.10.8, 14.4.3, 14.6-rc-1.
2. How severe is CVE-2022-41935? CVE-2022-41935 has a CVSS score of 5.3 (Medium). 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.platform:xwiki-platform-livetable-ui are affected by CVE-2022-41935? org.xwiki.platform:xwiki-platform-livetable-ui (maven) versions >= 12.10.11, < 13.10.8 is affected.
4. Is there a fix for CVE-2022-41935? Yes. CVE-2022-41935 is fixed in 13.10.8, 14.4.3, 14.6-rc-1. Upgrade to this version or later.
5. Is CVE-2022-41935 exploitable, and should I be worried? Whether CVE-2022-41935 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-41935 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-41935?
   • Upgrade org.xwiki.platform:xwiki-platform-livetable-ui to 13.10.8 or later
   • Upgrade org.xwiki.platform:xwiki-platform-livetable-ui to 14.4.3 or later
   • Upgrade org.xwiki.platform:xwiki-platform-livetable-ui to 14.6-rc-1 or later