Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-52vf-hvv3-98h7

MEDIUM

xwiki vulnerable to Improper Handling of Exceptional Conditions

Also known asCVE-2023-26479
Published
Mar 3, 2023
Updated
Nov 8, 2023
Affected
3 pkgs
Patched
3 / 3
Exploits
2 known

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk61th percentile+0.81%
0.00%0.53%1.06%1.58%0.2%1.1%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected
org.xwiki.platform:xwiki-platform-rendering-parserorg.xwiki.platform:xwiki-platform-rendering-parserorg.xwiki.platform:xwiki-platform-rendering-parser

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Users with write rights can insert well-formed content that is not handled well by the parser. For instance, with xwiki/2.1, inserting a deeply nested group blocks (((( ((( ((( ((( .... ))) ))) ))) ))) (see the generator below to produce a large payload) can lead to the parser throwing a StackOverflowError. As a consequence, some pages becomes unusable, including:

  • the user index (if the page containing the faulty content is a user page)
  • the page index

Note that on the page, the normal UI is completely missing and it is not possible to open the editor directly to revert the change as the stack overflow is already triggered while getting the title of the document. This means that it is quite difficult to remove this content once inserted.

Patches

This has been patched on XWiki 13.10.10, 14.4.6, and 14.9-rc-1.

Workarounds

A temporary solution to avoid Stack Overflow errors is to increase the memory allocated to the stack by using the -Xss JVM parameter (e.g., -Xss32m). This should allow the parser to pass and to fix the faulty content. Note that we did not evaluated the consequence on other aspects of the system (e.g., performances), and should be only be used as a temporary solution. Also, this does not prevent the issue to occur again with another content. Consequently, it is strongly advised to upgrade to a version where the issue has been patched.

References

For more information

If you have any questions or comments about this advisory:

Payload Generator

The Javascript code below produces 32768 nested group blocks, around the Hello text.

let result = "(((\nHello\n)))";
for (let i = 0; i < 15; ++i) {
  result = result.replace("Hello", result);
}
console.log(result);

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform:xwiki-platform-rendering-parser6.0&&< 13.10.1013.10.10
Mavenorg.xwiki.platform:xwiki-platform-rendering-parser14.0&&< 14.4.614.4.6
Mavenorg.xwiki.platform:xwiki-platform-rendering-parser14.5&&< 14.9-rc-114.9-rc-1
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-rendering-parser. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.xwiki.platform:xwiki-platform-rendering-parser to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-52vf-hvv3-98h7 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-52vf-hvv3-98h7 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-52vf-hvv3-98h7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Users with write rights can insert well-formed content that is not handled well by the parser. For instance, with `xwiki/2.1`, inserting a deeply nested group blocks (`((( ((( ((( ((( .... ))) ))) ))) )))` (see the generator below to produce a large payload) can lead to the parser throwing a `StackOverflowError`. As a consequence, some pages becomes unusable, including: - the user index (if the page containing the faulty content is a user page) - the page index Note that on the page, the normal UI is completely missing and it is not possible to open the editor directly to revert th
O3 Security · Impact-Aware SCA

Is GHSA-52vf-hvv3-98h7 in your dependencies?

O3 detects GHSA-52vf-hvv3-98h7 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.