CVE Vulnerabilities

CVE-2015-8624

Cross-Site Request Forgery (CSRF)

Published: Mar 23, 2017 | Modified: Apr 20, 2025
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

The User::matchEditToken function in includes/User.php in MediaWiki before 1.23.12, 1.24.x before 1.24.5, 1.25.x before 1.25.4, and 1.26.x before 1.26.1 does not perform token comparison in constant time before determining if a debugging message should be logged, which allows remote attackers to guess the edit token and bypass CSRF protection via a timing attack, a different vulnerability than CVE-2015-8623.

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.23.11 (including)
MediawikiMediawiki1.24.0 (including)1.24.0 (including)
MediawikiMediawiki1.24.1 (including)1.24.1 (including)
MediawikiMediawiki1.24.2 (including)1.24.2 (including)
MediawikiMediawiki1.24.3 (including)1.24.3 (including)
MediawikiMediawiki1.24.4 (including)1.24.4 (including)
MediawikiMediawiki1.25.0 (including)1.25.0 (including)
MediawikiMediawiki1.25.1 (including)1.25.1 (including)
MediawikiMediawiki1.25.2 (including)1.25.2 (including)
MediawikiMediawiki1.25.3 (including)1.25.3 (including)
MediawikiMediawiki1.26.0 (including)1.26.0 (including)
MediawikiUbuntuartful*
MediawikiUbuntuprecise*
MediawikiUbuntutrusty*
MediawikiUbuntuupstream*
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