CVE Vulnerabilities

CVE-2014-0570

Cross-Site Request Forgery (CSRF)

Published: Oct 15, 2014 | Modified: Sep 04, 2020
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

Cross-site request forgery (CSRF) vulnerability in Adobe ColdFusion 9.0 before Update 13, 9.0.1 before Update 12, 9.0.2 before Update 7, 10 before Update 14, and 11 before Update 2 allows remote attackers to hijack the authentication of unspecified victims via unknown vectors.

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
Coldfusion Adobe 9.0 (including) 9.0 (including)
Coldfusion Adobe 9.0-update_10 (including) 9.0-update_10 (including)
Coldfusion Adobe 9.0-update_12 (including) 9.0-update_12 (including)
Coldfusion Adobe 9.0.1 (including) 9.0.1 (including)
Coldfusion Adobe 9.0.1-update_11 (including) 9.0.1-update_11 (including)
Coldfusion Adobe 9.0.1-update_9 (including) 9.0.1-update_9 (including)
Coldfusion Adobe 9.0.2 (including) 9.0.2 (including)
Coldfusion Adobe 9.0.2-update_4 (including) 9.0.2-update_4 (including)
Coldfusion Adobe 9.0.2-update_6 (including) 9.0.2-update_6 (including)
Coldfusion Adobe 10.0 (including) 10.0 (including)
Coldfusion Adobe 10.0-update1 (including) 10.0-update1 (including)
Coldfusion Adobe 10.0-update11 (including) 10.0-update11 (including)
Coldfusion Adobe 10.0-update12 (including) 10.0-update12 (including)
Coldfusion Adobe 10.0-update2 (including) 10.0-update2 (including)
Coldfusion Adobe 10.0-update3 (including) 10.0-update3 (including)
Coldfusion Adobe 10.0-update4 (including) 10.0-update4 (including)
Coldfusion Adobe 10.0-update8 (including) 10.0-update8 (including)
Coldfusion Adobe 11.0 (including) 11.0 (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