CVE-2010-1767

Cross-site request forgery (CSRF) vulnerability in loader/DocumentThreadableLoader.cpp in WebCore in WebKit before r57041, as used in Google Chrome before 4.1.249.1059, allows remote attackers to hijack the authentication of unspecified victims via a crafted synchronous preflight XMLHttpRequest operation.

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

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]

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/111.html
• https://cwe.mitre.org/data/definitions/462.html
• https://cwe.mitre.org/data/definitions/467.html
• https://cwe.mitre.org/data/definitions/62.html

References

• http://code.google.com/p/chromium/issues/detail?id=39698
• http://googlechromereleases.blogspot.com/2010/04/stable-update-security-fixes.html
• http://lists.opensuse.org/opensuse-security-announce/2011-01/msg00006.html
• http://osvdb.org/64002
• http://secunia.com/advisories/39544
• http://secunia.com/advisories/41856
• http://secunia.com/advisories/43068
• http://security-tracker.debian.org/tracker/CVE-2010-1767
• http://trac.webkit.org/changeset/57041
• http://www.mandriva.com/security/advisories?name=MDVSA-2011:039
• http://www.securityfocus.com/bid/39603
• http://www.ubuntu.com/usn/USN-1006-1
• http://www.vupen.com/english/advisories/2010/2722
• http://www.vupen.com/english/advisories/2011/0212
• http://www.vupen.com/english/advisories/2011/0552
• https://bugs.webkit.org/show_bug.cgi?id=36843
• https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11140