CVE Vulnerabilities

CVE-2011-1482

Cross-Site Request Forgery (CSRF)

Published: Jun 21, 2011 | Modified: Nov 07, 2023
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

Multiple cross-site request forgery (CSRF) vulnerabilities in mainfile.php in Francisco Burzi PHP-Nuke 8.0 and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) add user accounts or (2) grant the administrative privilege to a user account, related to a Referer check that uses a substring comparison.

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
Php-nuke Phpnuke 5.6 5.6
Php-nuke Phpnuke 7.3 7.3
Php-nuke Phpnuke 7.4 7.4
Php-nuke Phpnuke 7.1 7.1
Php-nuke Phpnuke 5.0.1 5.0.1
Php-nuke Phpnuke 5.5 5.5
Php-nuke Phpnuke 7.9 7.9
Php-nuke Phpnuke 5.3 5.3
Php-nuke Phpnuke 6.9 6.9
Php-nuke Phpnuke 5.3.1 5.3.1
Php-nuke Phpnuke 5.0 5.0
Php-nuke Phpnuke 6.8 6.8
Php-nuke Phpnuke 6.6 6.6
Php-nuke Phpnuke 7.5 7.5
Php-nuke Phpnuke 7.2 7.2
Php-nuke Phpnuke 7.7 7.7
Php-nuke Phpnuke * 8.0
Php-nuke Phpnuke 5.2 5.2
Php-nuke Phpnuke 7.8 7.8
Php-nuke Phpnuke 6.0 6.0
Php-nuke Phpnuke 6.7 6.7
Php-nuke Phpnuke 7.0 7.0
Php-nuke Phpnuke 6.5 6.5
Php-nuke Phpnuke 5.1 5.1
Php-nuke Phpnuke 7.6 7.6
Php-nuke Phpnuke 5.4 5.4

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