Security
Headlines
HeadlinesLatestCVEs

Headline

GHSA-9j36-3cp4-rh4j: XWiki vulnerable to Code Injection in template provider administration

Impact

Any user with edit rights on any document (e.g., the own user profile) can execute code with programming rights, leading to remote code execution by following these steps:

  1. Set the title of any document you can edit (can be the user profile) to
    {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("Hello " + "from groovy!"){{/groovy}}{{/async}}
  1. Use the object editor to add an object of type XWiki.TemplateProviderClass (named “Template Provider Class”) to that document.
  2. Go to another document you can view (can be the home page) and append ?sheet=XWiki.AdminTemplatesSheet to the URL.

When the attack is successful, a template with name “Hello from groovy!” is displayed in the list while on fixed systems, the full title should be displayed.

Patches

This vulnerability has been patched in XWiki 13.10.11, 14.4.8, 14.10.1 and 15.0 RC1.

Workarounds

The vulnerability can be fixed by patching the code in the affected XWiki document as shown in the patch.

References

  • https://jira.xwiki.org/browse/XWIKI-20268
  • https://github.com/xwiki/xwiki-platform/commit/7bf7094f8ffac095f5d66809af7554c9cc44de09

For more information

If you have any questions or comments about this advisory:

ghsa
#vulnerability#git#java#rce#ssh#jira#maven
  1. GitHub Advisory Database
  2. GitHub Reviewed
  3. CVE-2023-29514

XWiki vulnerable to Code Injection in template provider administration

Critical severity GitHub Reviewed Published Apr 18, 2023 in xwiki/xwiki-platform • Updated Apr 20, 2023

Package

maven org.xwiki.platform.applications:xwiki-application-administration (Maven)

Affected versions

>= 1.35, <= 1.49

maven org.xwiki.platform:xwiki-platform-administration (Maven)

>= 3.1-milestone-1, < 4.2-milestone-1

maven org.xwiki.platform:xwiki-platform-administration-ui (Maven)

>= 4.2-milestone-1, < 13.10.11

>= 14.0-rc-1, < 14.4.8

>= 14.5, < 14.10.1

Impact

Any user with edit rights on any document (e.g., the own user profile) can execute code with programming rights, leading to remote code execution by following these steps:

  1. Set the title of any document you can edit (can be the user profile) to

    {{async async="true" cached="false" context="doc.reference"}}{{groovy}}println("Hello " + "from groovy!"){{/groovy}}{{/async}}
    
  2. Use the object editor to add an object of type XWiki.TemplateProviderClass (named “Template Provider Class”) to that document.

  3. Go to another document you can view (can be the home page) and append ?sheet=XWiki.AdminTemplatesSheet to the URL.

When the attack is successful, a template with name “Hello from groovy!” is displayed in the list while on fixed systems, the full title should be displayed.

Patches

This vulnerability has been patched in XWiki 13.10.11, 14.4.8, 14.10.1 and 15.0 RC1.

Workarounds

The vulnerability can be fixed by patching the code in the affected XWiki document as shown in the patch.

References

  • https://jira.xwiki.org/browse/XWIKI-20268
  • xwiki/xwiki-platform@7bf7094

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

References

  • GHSA-9j36-3cp4-rh4j
  • https://nvd.nist.gov/vuln/detail/CVE-2023-29514
  • xwiki/xwiki-platform@7bf7094
  • https://jira.xwiki.org/browse/XWIKI-20268

Published to the GitHub Advisory Database

Apr 20, 2023

Last updated

Apr 20, 2023

Related news

CVE-2023-29514: Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in template provider administration

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Any user with edit rights on any document (e.g., their own user profile) can execute code with programming rights, leading to remote code execution. This vulnerability has been patched in XWiki 13.10.11, 14.4.8, 14.10.1 and 15.0 RC1. Users are advised to upgrade. There are no known workarounds for this vulnerability.