CVE Vulnerabilities

CVE-2023-40572

Cross-Site Request Forgery (CSRF)

Published: Aug 24, 2023 | Modified: Sep 01, 2023
CVSS 3.x
8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. The create action is vulnerable to a CSRF attack, allowing script and thus remote code execution when targeting a user with script/programming right, thus compromising the confidentiality, integrity and availability of the whole XWiki installation. When a user with script right views this image and a log message ERROR foo - Script executed! appears in the log, the XWiki installation is vulnerable. This has been patched in XWiki 14.10.9 and 15.4RC1 by requiring a CSRF token for the actual page creation.

Weakness

The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.

Affected Software

Name Vendor Start Version End Version
Xwiki Xwiki * 14.10.9 (excluding)
Xwiki Xwiki 15.0 (including) 15.0 (including)
Xwiki Xwiki 15.0-rc1 (including) 15.0-rc1 (including)
Xwiki Xwiki 15.1 (including) 15.1 (including)
Xwiki Xwiki 15.1-rc1 (including) 15.1-rc1 (including)
Xwiki Xwiki 15.2 (including) 15.2 (including)
Xwiki Xwiki 15.2-rc1 (including) 15.2-rc1 (including)
Xwiki Xwiki 15.3 (including) 15.3 (including)
Xwiki Xwiki 15.3-rc1 (including) 15.3-rc1 (including)

Potential Mitigations

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330]
  • Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]
  • Use the “double-submitted cookie” method as described by Felten and Zeller:
  • When a user visits a site, the site should generate a pseudorandom value and set it as a cookie on the user’s machine. The site should require every form submission to include this value as a form value and also as a cookie value. When a POST request is sent to the site, the request should only be considered valid if the form value and the cookie value are the same.
  • Because of the same-origin policy, an attacker cannot read or modify the value stored in the cookie. To successfully submit a form on behalf of the user, the attacker would have to correctly guess the pseudorandom value. If the pseudorandom value is cryptographically strong, this will be prohibitively difficult.
  • This technique requires Javascript, so it may not work for browsers that have Javascript disabled. [REF-331]

References