GHSA-fxwr-4vq9-9vhj CVE-2022-36095
XWiki Cross-Site Request Forgery (CSRF) for actions on tags
Medium
Maven
- Severity
- 4.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.42%
- Chance of exploitation in the next 30 days. Higher than 36.12% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-352 Cross-Site Request Forgery (CSRF)
- Fix
13.10.5- Upgrade org.xwiki.platform:xwiki-platform-web-templates to this version or later
Description
Impact
It's possible to perform a CSRF attack for adding or removing tags on XWiki pages.
Patches
The problem has been patched in XWiki 13.10.5 and 14.3.
Workarounds
It's possible to fix the issue without upgrading by locally modifying the documentTags.vm template in your filesystem, to apply the changes exposed there: https://github.com/xwiki/xwiki-platform/commit/7ca56e40cf79a468cea54d3480b6b403f259f9ae.
References
https://jira.xwiki.org/browse/XWIKI-19550
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki
- Email us at security ML
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.xwiki.platform:xwiki-platform-web-templates | >= 2.0-milestone-1, < 13.10.5 |
13.10.5 |
| org.xwiki.platform:xwiki-platform-web-templates | >= 14.0, < 14.3 |
14.3 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.xwiki.platform:xwiki-platform-web-templates Maven → 13.10.5
- maven
<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-web-templates</artifactId><version>13.10.5</version></dependency>- gradle
implementation("org.xwiki.platform:xwiki-platform-web-templates:13.10.5")
Severity breakdown
CVSS 3.1 4.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
Weakness
CWE-352: Cross-Site Request Forgery (CSRF)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. 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]
- Implementation: Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
- Architecture and Design: Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330). [REF-332]
- Architecture and Design: Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.
- Architecture and Design: 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]
- Architecture and Design: Do not use the GET method for any request that triggers a state change.
- Implementation: Check the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-w4fj-87j5-f25c XWiki has Reflected Cross-Site Scripting (XSS) in page history compare | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-wvqx-m5px-6cmp XWiki Affected by Reflected Cross-Site Scripting (XSS) in Error Messages | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-7vpr-jm38-wr7w XWiki vulnerable to a reflected XSS via xredirect parameter in DeleteApplication | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-m9x4-w7p9-mxhx XWiki allows Reflected XSS in two templates | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-f963-4cq8-2gw7 In XWiki Platform, payloads stored in content is executed when a user with script/programming right edit them | High | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-692v-783f-mg8x XWiki Platform vulnerable to Cross-Site Scripting (XSS) through conflict resolution | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-93gh-jgjj-r929 XWiki Platform vulnerable to XSS with edit right in the create document form for existing pages | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-qcj9-gcpg-4w2w XWiki Platform web templates vulnerable to reflected XSS in the create document form if name validation is enabled | Critical | Also affects org.xwiki.platform:xwiki-platform-web-templates |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor