Authenticated code execution via unrestricted extension descriptions
Published Dec 12, 2024 · Updated Dec 13, 2024
Static code injection in affected XWiki Platform releases allows remote authenticated users to execute arbitrary server-side code. ExtensionCode.ExtensionSheet rendered the stored ExtensionClass description directly, so embedded Groovy macros ran without a restricted transformation context. A normal account without script or programming rights can add the object when the optional Extension Repository Application is installed, gaining programming-right code execution.
Summary
What happened
Static code injection in affected XWiki Platform releases allows remote authenticated users to execute arbitrary server-side code. ExtensionCode.ExtensionSheet rendered the stored ExtensionClass description directly, so embedded Groovy macros ran without a restricted transformation context. A normal account without script or programming rights can add the object when the optional Extension Repository Application is installed, gaining programming-right code execution.
The record
- CVE
- CVE-2024-55662
- Published
- Dec 12, 2024
- Updated
- Dec 13, 2024
- Vendor
- CryptPad
- Product
- XWiki Platform
- Classifications
- CWE-94, CWE-863, CWE-96, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 12, 2024CVE publishedPublication date reported by the CVE source.
- Dec 13, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 16.0.0-rc-1, < 16.3.0
- Affected versionversion=>= 3.3-milestone-1, < 15.10.9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream ExtensionClass description reproduction procedureproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo