CVE Vulnerabilities

CVE-2007-5032

Cross-Site Request Forgery (CSRF)

Published: Sep 21, 2007 | Modified: Oct 15, 2018
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

Cross-site request forgery (CSRF) vulnerability in admin.php in Francisco Burzi PHP-Nuke allows remote attackers to add administrative accounts via an AddAuthor action with modified add_name and add_radminsuper parameters.

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 Francisco_burzi * 1.0 (including)
Php-nuke Francisco_burzi * 2.5 (including)
Php-nuke Francisco_burzi * 3.0 (including)
Php-nuke Francisco_burzi * 4.0 (including)
Php-nuke Francisco_burzi * 4.0.4 (including)
Php-nuke Francisco_burzi * 4.3 (including)
Php-nuke Francisco_burzi * 4.4 (including)
Php-nuke Francisco_burzi * 4.4.1a (including)
Php-nuke Francisco_burzi * 5.0 (including)
Php-nuke Francisco_burzi * 5.0.1 (including)
Php-nuke Francisco_burzi * 5.1 (including)
Php-nuke Francisco_burzi * 5.2 (including)
Php-nuke Francisco_burzi * 5.2a (including)
Php-nuke Francisco_burzi * 5.3.1 (including)
Php-nuke Francisco_burzi * 5.4 (including)
Php-nuke Francisco_burzi * 5.5 (including)
Php-nuke Francisco_burzi * 5.6 (including)
Php-nuke Francisco_burzi * 6.0 (including)
Php-nuke Francisco_burzi * 6.5 (including)
Php-nuke Francisco_burzi * 6.5_beta1 (including)
Php-nuke Francisco_burzi * 6.5_final (including)
Php-nuke Francisco_burzi * 6.5_rc1 (including)
Php-nuke Francisco_burzi * 6.5_rc2 (including)
Php-nuke Francisco_burzi * 6.5_rc3 (including)
Php-nuke Francisco_burzi * 6.6 (including)
Php-nuke Francisco_burzi * 6.7 (including)
Php-nuke Francisco_burzi * 6.8 (including)
Php-nuke Francisco_burzi * 6.9 (including)
Php-nuke Francisco_burzi * 7.0 (including)
Php-nuke Francisco_burzi * 7.0_final (including)
Php-nuke Francisco_burzi * 7.1 (including)
Php-nuke Francisco_burzi * 7.2 (including)
Php-nuke Francisco_burzi * 7.3 (including)
Php-nuke Francisco_burzi * 7.4 (including)
Php-nuke Francisco_burzi * 7.5 (including)
Php-nuke Francisco_burzi * 7.6 (including)
Php-nuke Francisco_burzi * 7.7 (including)
Php-nuke Francisco_burzi * 7.8 (including)
Php-nuke Francisco_burzi * 7.8_patched_3.2 (including)
Php-nuke Francisco_burzi * 7.9 (including)
Php-nuke Francisco_burzi * 8.0_final (including)

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