Skip to content

Scheduler in subwiki allows scheduling operations for any main wiki user

Moderate
manuelleduc published GHSA-cwq6-mjmx-47p6 Dec 12, 2024

Package

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

Affected versions

>= 1.2-milestone-2, < 15.10.9
>= 16.0.0-rc-1, < 16.3.0

Patched versions

15.10.9
16.3.0

Description

Impact

Any user with an account on the main wiki could run scheduling operations on subwikis.
To reproduce, as a user on the main wiki without any special right, view the document Scheduler.WebHome in a subwiki. Then, click on any operation (e.g., Trigger) on any job. If the operation is successful, then the instance is vulnerable.

Patches

This has been patched in XWiki 15.10.9 and 16.3.0.

Workarounds

If you have subwikis where the Job Scheduler is enabled, you can edit the objects on Scheduler.WebPreferences to match 54bcc5a#diff-8e274bd0065e319a34090339de6dfe56193144d15fd71c52c1be7272254728b4.

References

For more information

If you have any questions or comments about this advisory:

Severity

Moderate

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

CVE ID

CVE-2024-55876

Weaknesses