CVE Vulnerabilities

CVE-2010-3694

Cross-Site Request Forgery (CSRF)

Published: Nov 09, 2010 | Modified: Jul 12, 2011
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 the Horde Application Framework before 3.3.9 allows remote attackers to hijack the authentication of unspecified victims for requests to a preference form.

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
Horde_application_framework Horde 1.0.3 1.0.3
Horde_application_framework Horde 1.1.1 1.1.1
Horde_application_framework Horde 1.3.0 1.3.0
Horde_application_framework Horde 1.3.1 1.3.1
Horde_application_framework Horde 1.3.2 1.3.2
Horde_application_framework Horde 1.3.3 1.3.3
Horde_application_framework Horde 1.3.4 1.3.4
Horde_application_framework Horde 1.3.5 1.3.5
Horde_application_framework Horde 2.0 2.0
Horde_application_framework Horde 2.0 2.0
Horde_application_framework Horde 2.0 2.0
Horde_application_framework Horde 2.0 2.0
Horde_application_framework Horde 2.1 2.1
Horde_application_framework Horde 2.2 2.2
Horde_application_framework Horde 2.2.1 2.2.1
Horde_application_framework Horde 2.2.2 2.2.2
Horde_application_framework Horde 2.2.3 2.2.3
Horde_application_framework Horde 2.2.4 2.2.4
Horde_application_framework Horde 2.2.5 2.2.5
Horde_application_framework Horde 2.2.6 2.2.6
Horde_application_framework Horde 2.2.6 2.2.6
Horde_application_framework Horde 2.2.7 2.2.7
Horde_application_framework Horde 2.2.8 2.2.8
Horde_application_framework Horde 2.2.9 2.2.9
Horde_application_framework Horde 3.0 3.0
Horde_application_framework Horde 3.0 3.0
Horde_application_framework Horde 3.0 3.0
Horde_application_framework Horde 3.0 3.0
Horde_application_framework Horde 3.0 3.0
Horde_application_framework Horde 3.0 3.0
Horde_application_framework Horde 3.0.1 3.0.1
Horde_application_framework Horde 3.0.2 3.0.2
Horde_application_framework Horde 3.0.3 3.0.3
Horde_application_framework Horde 3.0.3 3.0.3
Horde_application_framework Horde 3.0.4 3.0.4
Horde_application_framework Horde 3.0.4 3.0.4
Horde_application_framework Horde 3.0.4 3.0.4
Horde_application_framework Horde 3.0.5 3.0.5
Horde_application_framework Horde 3.0.5 3.0.5
Horde_application_framework Horde 3.0.5 3.0.5
Horde_application_framework Horde 3.0.6 3.0.6
Horde_application_framework Horde 3.0.6 3.0.6
Horde_application_framework Horde 3.0.7 3.0.7
Horde_application_framework Horde 3.0.8 3.0.8
Horde_application_framework Horde 3.0.9 3.0.9
Horde_application_framework Horde 3.0.10 3.0.10
Horde_application_framework Horde 3.0.11 3.0.11
Horde_application_framework Horde 3.0.12 3.0.12
Horde_application_framework Horde 3.1 3.1
Horde_application_framework Horde 3.1 3.1
Horde_application_framework Horde 3.1 3.1
Horde_application_framework Horde 3.1 3.1
Horde_application_framework Horde 3.1.1 3.1.1
Horde_application_framework Horde 3.1.2 3.1.2
Horde_application_framework Horde 3.1.3 3.1.3
Horde_application_framework Horde 3.1.4 3.1.4
Horde_application_framework Horde 3.1.4 3.1.4
Horde_application_framework Horde 3.1.5 3.1.5
Horde_application_framework Horde 3.1.6 3.1.6
Horde_application_framework Horde 3.1.7 3.1.7
Horde_application_framework Horde 3.1.8 3.1.8
Horde_application_framework Horde 3.1.9 3.1.9
Horde_application_framework Horde 3.2 3.2
Horde_application_framework Horde 3.2 3.2
Horde_application_framework Horde 3.2 3.2
Horde_application_framework Horde 3.2 3.2
Horde_application_framework Horde 3.2 3.2
Horde_application_framework Horde 3.2 3.2
Horde_application_framework Horde 3.2.1 3.2.1
Horde_application_framework Horde 3.2.2 3.2.2
Horde_application_framework Horde 3.2.3 3.2.3
Horde_application_framework Horde 3.2.4 3.2.4
Horde_application_framework Horde 3.2.5 3.2.5
Horde_application_framework Horde 3.3 3.3
Horde_application_framework Horde 3.3 3.3
Horde_application_framework Horde 3.3.1 3.3.1
Horde_application_framework Horde 3.3.2 3.3.2
Horde_application_framework Horde 3.3.3 3.3.3
Horde_application_framework Horde 3.3.4 3.3.4
Horde_application_framework Horde 3.3.4 3.3.4
Horde_application_framework Horde 3.3.5 3.3.5
Horde_application_framework Horde 3.3.6 3.3.6
Horde_application_framework Horde 3.3.7 3.3.7
Horde_application_framework Horde * 3.3.8
Horde3 Ubuntu dapper *
Horde3 Ubuntu hardy *
Horde3 Ubuntu karmic *
Horde3 Ubuntu lucid *
Horde3 Ubuntu maverick *
Horde3 Ubuntu upstream *

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