XWiki's REST APIs don't enforce any limits, leading to unavailability and OOM in large wikis
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 16.10.11, 17.4.4, 17.7.0-rc-1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: partial
Summary
XWiki is an open-source wiki software platform. Versions 16.10.10 and below, 17.0.0-rc-1 through 17.4.3 and 17.5.0-rc-1 through 17.6.0 contain a REST API which doesn't enforce any limits for the number of items that can be requested in a single request at the moment. Depending on the number of pages in the wiki and the memory configuration, this can lead to slowness and unavailability of the wiki. As an example, the /rest/wikis/xwiki/spaces resource returns all spaces on the wiki by default, which are basically all pages. This issue is fixed in versions 17.4.4 and 16.10.11.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- xwiki xwiki-platform
fixed in 16.10.11; From 17.0.0-rc-1 · fixed in 17.4.4; From 17.5.0-rc-1 · fixed in 17.7.0-rc-1
- org.xwiki.platform:xwiki-platform-rest-serverMaven
fixed in 16.10.11
- org.xwiki.platform:xwiki-platform-rest-serverMaven
From 17.0.0-rc-1 · fixed in 17.4.4
- org.xwiki.platform:xwiki-platform-rest-serverMaven
From 17.5.0-rc-1 · fixed in 17.7.0-rc-1