CVE Vulnerabilities

CVE-2014-9276

Cross-Site Request Forgery (CSRF)

Published: Jan 04, 2015 | Modified: Apr 12, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5.1 MEDIUM
AV:N/AC:H/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

Cross-site request forgery (CSRF) vulnerability in the Special:ExpandedTemplates page in MediaWiki before 1.19.22, 1.20.x through 1.22.x before 1.22.14, and 1.23.x before 1.23.7, when $wgRawHTML is set to true, allows remote attackers to hijack the authentication of users with edit permissions for requests that cross-site scripting (XSS) attacks via the wpInput parameter, which is not properly handled in the preview.

Weakness

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.

Affected Software

NameVendorStart VersionEnd Version
MediawikiMediawiki*1.19.21 (including)
MediawikiMediawiki1.20 (including)1.20 (including)
MediawikiMediawiki1.20.1 (including)1.20.1 (including)
MediawikiMediawiki1.20.2 (including)1.20.2 (including)
MediawikiMediawiki1.20.3 (including)1.20.3 (including)
MediawikiMediawiki1.20.4 (including)1.20.4 (including)
MediawikiMediawiki1.20.5 (including)1.20.5 (including)
MediawikiMediawiki1.20.6 (including)1.20.6 (including)
MediawikiMediawiki1.20.7 (including)1.20.7 (including)
MediawikiMediawiki1.20.8 (including)1.20.8 (including)
MediawikiMediawiki1.21 (including)1.21 (including)
MediawikiMediawiki1.21.1 (including)1.21.1 (including)
MediawikiMediawiki1.21.2 (including)1.21.2 (including)
MediawikiMediawiki1.21.3 (including)1.21.3 (including)
MediawikiMediawiki1.21.4 (including)1.21.4 (including)
MediawikiMediawiki1.21.5 (including)1.21.5 (including)
MediawikiMediawiki1.21.6 (including)1.21.6 (including)
MediawikiMediawiki1.21.7 (including)1.21.7 (including)
MediawikiMediawiki1.21.8 (including)1.21.8 (including)
MediawikiMediawiki1.21.9 (including)1.21.9 (including)
MediawikiMediawiki1.21.10 (including)1.21.10 (including)
MediawikiMediawiki1.21.11 (including)1.21.11 (including)
MediawikiMediawiki1.22.0 (including)1.22.0 (including)
MediawikiMediawiki1.22.1 (including)1.22.1 (including)
MediawikiMediawiki1.22.2 (including)1.22.2 (including)
MediawikiMediawiki1.22.3 (including)1.22.3 (including)
MediawikiMediawiki1.22.4 (including)1.22.4 (including)
MediawikiMediawiki1.22.5 (including)1.22.5 (including)
MediawikiMediawiki1.22.6 (including)1.22.6 (including)
MediawikiMediawiki1.22.7 (including)1.22.7 (including)
MediawikiMediawiki1.22.8 (including)1.22.8 (including)
MediawikiMediawiki1.22.10 (including)1.22.10 (including)
MediawikiMediawiki1.22.11 (including)1.22.11 (including)
MediawikiMediawiki1.22.12 (including)1.22.12 (including)
MediawikiMediawiki1.22.13 (including)1.22.13 (including)
MediawikiMediawiki1.23.0 (including)1.23.0 (including)
MediawikiMediawiki1.23.1 (including)1.23.1 (including)
MediawikiMediawiki1.23.2 (including)1.23.2 (including)
MediawikiMediawiki1.23.3 (including)1.23.3 (including)
MediawikiMediawiki1.23.4 (including)1.23.4 (including)
MediawikiMediawiki1.23.5 (including)1.23.5 (including)
MediawikiMediawiki1.23.6 (including)1.23.6 (including)
MediawikiUbuntuartful*
MediawikiUbuntulucid*
MediawikiUbuntuprecise*
MediawikiUbuntutrusty*
MediawikiUbuntuutopic*
MediawikiUbuntuvivid*
MediawikiUbuntuwily*
MediawikiUbuntuyakkety*
MediawikiUbuntuzesty*

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 [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]
  • 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