CVE Vulnerabilities

CVE-2012-2128

Cross-Site Request Forgery (CSRF)

Published: Aug 27, 2012 | Modified: May 17, 2024
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

Cross-site request forgery (CSRF) vulnerability in doku.php in DokuWiki 2012-01-25 Angua allows remote attackers to hijack the authentication of administrators for requests that add arbitrary users. NOTE: this issue has been disputed by the vendor, who states that it is resultant from CVE-2012-2129: the exploit code simply uses the XSS hole to extract a valid CSRF token.

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
Dokuwiki Andreas_gohr 2012-01-25 (including) 2012-01-25 (including)
Dokuwiki Ubuntu artful *
Dokuwiki Ubuntu hardy *
Dokuwiki Ubuntu lucid *
Dokuwiki Ubuntu natty *
Dokuwiki Ubuntu oneiric *
Dokuwiki Ubuntu precise *
Dokuwiki Ubuntu quantal *
Dokuwiki Ubuntu raring *
Dokuwiki Ubuntu saucy *
Dokuwiki Ubuntu upstream *
Dokuwiki Ubuntu utopic *
Dokuwiki Ubuntu vivid *
Dokuwiki Ubuntu wily *
Dokuwiki Ubuntu yakkety *
Dokuwiki Ubuntu zesty *

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