CVE Vulnerabilities

CVE-2011-1325

Cross-Site Request Forgery (CSRF)

Published: May 13, 2011 | Modified: May 26, 2011
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Cross-site request forgery (CSRF) vulnerability in EC-CUBE before 2.11.0 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
Ec-cube Lockon * 2.11.0 (including)
Ec-cube Lockon 1.1.0-beta (including) 1.1.0-beta (including)
Ec-cube Lockon 1.1.1 (including) 1.1.1 (including)
Ec-cube Lockon 1.2.0-beta (including) 1.2.0-beta (including)
Ec-cube Lockon 1.3.0 (including) 1.3.0 (including)
Ec-cube Lockon 1.3.0-beta (including) 1.3.0-beta (including)
Ec-cube Lockon 1.3.1 (including) 1.3.1 (including)
Ec-cube Lockon 1.3.1-a (including) 1.3.1-a (including)
Ec-cube Lockon 1.3.2 (including) 1.3.2 (including)
Ec-cube Lockon 1.3.3 (including) 1.3.3 (including)
Ec-cube Lockon 1.3.4 (including) 1.3.4 (including)
Ec-cube Lockon 1.3.4-community (including) 1.3.4-community (including)
Ec-cube Lockon 1.4.0-a-beta (including) 1.4.0-a-beta (including)
Ec-cube Lockon 1.4.0-beta (including) 1.4.0-beta (including)
Ec-cube Lockon 1.4.1-beta (including) 1.4.1-beta (including)
Ec-cube Lockon 1.4.2-beta (including) 1.4.2-beta (including)
Ec-cube Lockon 1.4.3-a-beta (including) 1.4.3-a-beta (including)
Ec-cube Lockon 1.4.3-b-beta (including) 1.4.3-b-beta (including)
Ec-cube Lockon 1.4.3-beta (including) 1.4.3-beta (including)
Ec-cube Lockon 1.4.4-beta (including) 1.4.4-beta (including)
Ec-cube Lockon 1.4.5 (including) 1.4.5 (including)
Ec-cube Lockon 1.4.6 (including) 1.4.6 (including)
Ec-cube Lockon 1.4.7 (including) 1.4.7 (including)
Ec-cube Lockon 1.5.0-beta (including) 1.5.0-beta (including)
Ec-cube Lockon 2.0.0-beta (including) 2.0.0-beta (including)
Ec-cube Lockon 2.0.1 (including) 2.0.1 (including)
Ec-cube Lockon 2.0.1-a (including) 2.0.1-a (including)
Ec-cube Lockon 2.1.0-beta (including) 2.1.0-beta (including)
Ec-cube Lockon 2.1.2 (including) 2.1.2 (including)
Ec-cube Lockon 2.1.2-a (including) 2.1.2-a (including)
Ec-cube Lockon 2.2.0-beta (including) 2.2.0-beta (including)
Ec-cube Lockon 2.2.1-one (including) 2.2.1-one (including)
Ec-cube Lockon 2.3.0 (including) 2.3.0 (including)
Ec-cube Lockon 2.3.0-rc1 (including) 2.3.0-rc1 (including)
Ec-cube Lockon 2.3.1 (including) 2.3.1 (including)
Ec-cube Lockon 2.3.3 (including) 2.3.3 (including)
Ec-cube Lockon 2.3.4 (including) 2.3.4 (including)
Ec-cube Lockon 2.4.0 (including) 2.4.0 (including)
Ec-cube Lockon 2.4.0-rc1 (including) 2.4.0-rc1 (including)
Ec-cube Lockon 2.4.1 (including) 2.4.1 (including)
Ec-cube Lockon 2.4.2 (including) 2.4.2 (including)
Ec-cube Lockon 2.4.3 (including) 2.4.3 (including)
Ec-cube Lockon 2.4.4 (including) 2.4.4 (including)
Ec-cube Lockon 2.5.0-alpha (including) 2.5.0-alpha (including)
Ec-cube Lockon 2.5.0-alpha2 (including) 2.5.0-alpha2 (including)
Ec-cube Lockon 2.11.0 (including) 2.11.0 (including)
Ec-cube Lockon 2.11.0-beta (including) 2.11.0-beta (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