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

GHSA-8959-rfxh-r4j4

HIGH

XWiki vulnerable to Denial of Service attack through attachments

Also known asCVE-2024-21651
Published
Jan 8, 2024
Updated
Jan 9, 2024
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk46th percentile+0.14%
0.00%0.38%0.76%1.14%0.4%0.6%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-distribution-warorg.xwiki.platform:xwiki-platform-distribution-warorg.xwiki.platform:xwiki-platform-distribution-war

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

A user able to attach a file to a page can post a malformed TAR file by manipulating file modification times headers, which when parsed by Tika, could cause a denial of service issue via CPU consumption.

Patches

This vulnerability has been patched in XWiki 14.10.18, 15.5.3 and 15.8 RC1.

Workarounds

The workaround is to download commons-compress 1.24 and replace the one located in XWiki WEB-INF/lib/ folder.

References

https://jira.xwiki.org/browse/XCOMMONS-2796

For more information

If you have any questions or comments about this advisory:

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform:xwiki-platform-distribution-war14.10&&< 14.10.1814.10.18
Mavenorg.xwiki.platform:xwiki-platform-distribution-war15.0-rc-1&&< 15.5.315.5.3
Mavenorg.xwiki.platform:xwiki-platform-distribution-war15.6-rc-1&&< 15.8-rc-115.8-rc-1

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-distribution-war. 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-distribution-war to 14.10.18 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8959-rfxh-r4j4 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-8959-rfxh-r4j4 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-8959-rfxh-r4j4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A user able to attach a file to a page can post a malformed TAR file by manipulating file modification times headers, which when parsed by Tika, could cause a denial of service issue via CPU consumption. ### Patches This vulnerability has been patched in XWiki 14.10.18, 15.5.3 and 15.8 RC1. ### Workarounds The workaround is to download [commons-compress 1.24](https://search.maven.org/remotecontent?filepath=org/apache/commons/commons-compress/1.24.0/commons-compress-1.24.0.jar) and replace the one located in XWiki `WEB-INF/lib/` folder. ### References https://jira.xwiki.org/br
O3 Security · Impact-Aware SCA

Is GHSA-8959-rfxh-r4j4 in your dependencies?

O3 detects GHSA-8959-rfxh-r4j4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.