CVE Vulnerabilities

CVE-2012-5500

Cross-Site Request Forgery (CSRF)

Published: Nov 03, 2014 | Modified: Apr 12, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:N
RedHat/V2
2.6 LOW
AV:N/AC:H/Au:N/C:N/I:P/A:N
RedHat/V3
Ubuntu
root.io logo minimus.io logo echo.ai logo

The batch id change script (renameObjectsByPaths.py) in Plone before 4.2.3 and 4.3 before beta 1 allows remote attackers to change the titles of content items by leveraging a valid CSRF token in a crafted request.

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
PlonePlone*4.2.2 (including)
PlonePlone1.0 (including)1.0 (including)
PlonePlone1.0.1 (including)1.0.1 (including)
PlonePlone1.0.2 (including)1.0.2 (including)
PlonePlone1.0.3 (including)1.0.3 (including)
PlonePlone1.0.4 (including)1.0.4 (including)
PlonePlone1.0.5 (including)1.0.5 (including)
PlonePlone1.0.6 (including)1.0.6 (including)
PlonePlone2.0 (including)2.0 (including)
PlonePlone2.0.1 (including)2.0.1 (including)
PlonePlone2.0.2 (including)2.0.2 (including)
PlonePlone2.0.3 (including)2.0.3 (including)
PlonePlone2.0.4 (including)2.0.4 (including)
PlonePlone2.0.5 (including)2.0.5 (including)
PlonePlone2.1 (including)2.1 (including)
PlonePlone2.1.1 (including)2.1.1 (including)
PlonePlone2.1.2 (including)2.1.2 (including)
PlonePlone2.1.3 (including)2.1.3 (including)
PlonePlone2.1.4 (including)2.1.4 (including)
PlonePlone2.5 (including)2.5 (including)
PlonePlone2.5.1 (including)2.5.1 (including)
PlonePlone2.5.2 (including)2.5.2 (including)
PlonePlone2.5.3 (including)2.5.3 (including)
PlonePlone2.5.4 (including)2.5.4 (including)
PlonePlone2.5.5 (including)2.5.5 (including)
PlonePlone3.0 (including)3.0 (including)
PlonePlone3.0.1 (including)3.0.1 (including)
PlonePlone3.0.2 (including)3.0.2 (including)
PlonePlone3.0.3 (including)3.0.3 (including)
PlonePlone3.0.4 (including)3.0.4 (including)
PlonePlone3.0.5 (including)3.0.5 (including)
PlonePlone3.0.6 (including)3.0.6 (including)
PlonePlone3.1 (including)3.1 (including)
PlonePlone3.1.1 (including)3.1.1 (including)
PlonePlone3.1.2 (including)3.1.2 (including)
PlonePlone3.1.3 (including)3.1.3 (including)
PlonePlone3.1.4 (including)3.1.4 (including)
PlonePlone3.1.5.1 (including)3.1.5.1 (including)
PlonePlone3.1.6 (including)3.1.6 (including)
PlonePlone3.1.7 (including)3.1.7 (including)
PlonePlone3.2 (including)3.2 (including)
PlonePlone3.2.1 (including)3.2.1 (including)
PlonePlone3.2.2 (including)3.2.2 (including)
PlonePlone3.2.3 (including)3.2.3 (including)
PlonePlone3.3 (including)3.3 (including)
PlonePlone3.3.1 (including)3.3.1 (including)
PlonePlone3.3.2 (including)3.3.2 (including)
PlonePlone3.3.3 (including)3.3.3 (including)
PlonePlone3.3.4 (including)3.3.4 (including)
PlonePlone3.3.5 (including)3.3.5 (including)
PlonePlone4.0 (including)4.0 (including)
PlonePlone4.0.1 (including)4.0.1 (including)
PlonePlone4.0.2 (including)4.0.2 (including)
PlonePlone4.0.3 (including)4.0.3 (including)
PlonePlone4.0.4 (including)4.0.4 (including)
PlonePlone4.0.5 (including)4.0.5 (including)
PlonePlone4.0.6.1 (including)4.0.6.1 (including)
PlonePlone4.1 (including)4.1 (including)
PlonePlone4.1.4 (including)4.1.4 (including)
PlonePlone4.1.5 (including)4.1.5 (including)
PlonePlone4.1.6 (including)4.1.6 (including)
PlonePlone4.2 (including)4.2 (including)
PlonePlone4.2.1 (including)4.2.1 (including)
PlonePlone4.3 (including)4.3 (including)
Red Hat Enterprise Linux 5RedHatconga-0:0.12.2-81.el5*

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