Skip to content

Arbitrary filesystem write access from velocity.

High severity GitHub Reviewed Published Apr 28, 2022 in xwiki/xwiki-commons • Updated Jan 30, 2023

Package

maven org.xwiki.commons:xwiki-commons-velocity (Maven)

Affected versions

>= 2.3.0, < 12.6.7
>= 12.7.0, < 12.10.3

Patched versions

12.6.7
12.10.3

Description

Impact

The velocity scripts is not properly sandboxed against using the Java File API to perform read or write operations on the filesystem. Now writing an attacking script in velocity requires the Script rights in XWiki so not all users can use it, and it also requires finding an XWiki API which returns a File.

Patches

The problem has been patched on versions 12.6.7, 12.10.3 and 13.0RC1.

Workarounds

There's no easy workaround for fixing this vulnerability other than upgrading and being careful when giving Script rights.

References

https://jira.xwiki.org/browse/XWIKI-5168

For more information

If you have any questions or comments about this advisory:

References

@tmortagne tmortagne published to xwiki/xwiki-commons Apr 28, 2022
Published to the GitHub Advisory Database Apr 28, 2022
Reviewed Apr 28, 2022
Published by the National Vulnerability Database May 2, 2022
Last updated Jan 30, 2023

Severity

High

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
High
Privileges required
Low
User interaction
None
Scope
Unchanged
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:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.271%
(69th percentile)

Weaknesses

CVE ID

CVE-2022-24897

GHSA ID

GHSA-cvx5-m8vg-vxgc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.