CVE Vulnerabilities

CVE-2013-6443

Cross-Site Request Forgery (CSRF)

Published: Jan 23, 2014 | Modified: Jan 23, 2014
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
3.5 MODERATE
AV:N/AC:M/Au:S/C:N/I:P/A:N
RedHat/V3
Ubuntu

CloudForms 3.0 Management Engine before 5.2.1.6 allows remote attackers to bypass the Ruby on Rails protect_from_forgery mechanism and conduct cross-site request forgery (CSRF) attacks via a destructive action in a request.

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
Cloudforms Redhat 3.0 (including) 3.0 (including)
Cloudforms_3.0_management_engine Redhat * 5.2.1 (including)
Cloudforms_3.0_management_engine Redhat 5.2 (including) 5.2 (including)
CloudForms Management Engine 5.x RedHat cfme-0:5.2.1.8-1.el6cf *
CloudForms Management Engine 5.x RedHat ruby193-rubygem-activerecord-1:3.2.13-4.el6cf *
CloudForms Management Engine 5.x RedHat ruby193-rubygem-linux_admin-0:0.5.6-1.el6cf *

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