CWE
22 23
Advisory Published
Advisory Published
Updated

CVE-2023-37913: org.xwiki.platform:xwiki-platform-office-importer vulnerable to arbitrary server side file writing from account through office converter

First published: Wed Oct 25 2023(Updated: )

### Impact Triggering the office converter with a specially crafted file name allows writing the attachment's content to an attacker-controlled location on the server as long as the Java process has write access to that location. In particular in the combination with attachment moving, a feature introduced in XWiki 14.0, this is easy to reproduce but it also possible to reproduce in versions as old as XWiki 3.5 by uploading the attachment through the REST API which doesn't remove `/` or `\` from the filename. As the mime type of the attachment doesn't matter for the exploitation, this could e.g., be used to replace the `jar`-file of an extension which would allow executing arbitrary Java code and thus impact the confidentiality, integrity and availability of the XWiki installation. To reproduce the issue on versions since XWiki 14.0, execute the following steps: 1. Activate the office server 2. Upload an arbitrary file with the extension .doc, e.g., to your user profile (you can use a regular plain text file, only the extension matters). 3. Use the attachment move feature to rename the file to ../../../../../tmp/Hello from XWiki.txt where the latter part is the location of a file you want to write on the server. The number of ../ depends on the directory depth, the provided example should work on Linux with the demo distribution. 4. Click the "preview" link to trigger the office converter For information how to reproduce on older versions, see the [Jira issue](https://jira.xwiki.org/browse/XWIKI-20715). To the best of our knowledge, this attack is not possible when the office conversion process doesn't run as the code fails before the file is written. ### Patches This vulnerability has been patched in XWiki 14.10.8 and 15.3RC1. ### Workarounds There are no known workarounds apart from disabling the office converter. ### References * https://jira.xwiki.org/browse/XWIKI-20715 * https://github.com/xwiki/xwiki-platform/commit/45d182a4141ff22f3ff289cf71e4669bdc714544

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Xwiki Xwiki>=3.5<14.10.8
Xwiki Xwiki>=15.0<15.3
maven/org.xwiki.platform:xwiki-platform-office-importer>=15.0-rc-1<15.3-rc-1
15.3-rc-1
maven/org.xwiki.platform:xwiki-platform-office-importer>=3.5-milestone-1<14.10.8
14.10.8

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2023-37913?

    The severity of CVE-2023-37913 is critical.

  • How does CVE-2023-37913 impact the system?

    CVE-2023-37913 allows an attacker to write the attachment's content to an attacker-controlled location on the server if the Java process has write access to that location.

  • Which packages are affected by CVE-2023-37913?

    org.xwiki.platform:xwiki-platform-office-importer versions 15.0-rc-1 to 15.3-rc-1 and 3.5-milestone-1 to 14.10.8 are affected by CVE-2023-37913.

  • How can I fix CVE-2023-37913?

    Upgrade org.xwiki.platform:xwiki-platform-office-importer to version 15.3-rc-1 or later, or version 14.10.8 or later to fix CVE-2023-37913.

  • Where can I find more information about CVE-2023-37913?

    You can find more information about CVE-2023-37913 in the following references: [link1](https://github.com/xwiki/xwiki-platform/security/advisories/GHSA-vcvr-v426-3m3m), [link2](https://github.com/xwiki/xwiki-platform/commit/45d182a4141ff22f3ff289cf71e4669bdc714544), [link3](https://jira.xwiki.org/browse/XWIKI-20715).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203