Skip to content

Run Shell Command allows Cross-Site Request Forgery

Critical severity GitHub Reviewed Published Nov 20, 2023 in xwiki-contrib/application-admintools • Updated Nov 20, 2023

Package

maven org.xwiki.contrib:xwiki-application-admintools (Maven)

Affected versions

>= 4.4, < 4.5.1

Patched versions

4.5.1

Description

Impact

A cross site request forgery vulnerability in the admin tool for executing shell commands on the server allows an attacker to execute arbitrary shell commands by tricking an admin into loading the URL with the shell command. A very simple possibility for an attack are comments. When the attacker can leave a comment on any page in the wiki it is sufficient to include an image with an URL like /xwiki/bin/view/Admin/RunShellCommand?command=touch%20/tmp/attacked in the comment. When an admin views the comment, the file /tmp/attacked will be created on the server. The output of the command is also vulnerable to XWiki syntax injection which offers a simple way to execute Groovy in the context of the XWiki installation and thus an even easier way to compromise the integrity and confidentiality of the whole XWiki installation.

Patches

This has been patched by adding a form token check in version 4.5.1 of the admin tools.

Workarounds

The patch can be applied manually to the affected wiki pages. Alternatively, the document Admin.RunShellCommand can also be deleted if the possibility to run shell commands isn't needed.

References

References

Published by the National Vulnerability Database Nov 20, 2023
Published to the GitHub Advisory Database Nov 20, 2023
Reviewed Nov 20, 2023
Last updated Nov 20, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

EPSS score

0.075%
(35th percentile)

Weaknesses

CVE ID

CVE-2023-48292

GHSA ID

GHSA-8jpr-ff92-hpf9
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.