CVE Vulnerabilities

CVE-2010-0540

Cross-Site Request Forgery (CSRF)

Published: Jun 17, 2010 | Modified: Apr 11, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
6 MEDIUM
AV:N/AC:M/Au:S/C:P/I:P/A:P
RedHat/V2
5.1 MODERATE
AV:N/AC:H/Au:N/C:P/I:P/A:P
RedHat/V3
Ubuntu
MEDIUM

Cross-site request forgery (CSRF) vulnerability in the web interface in CUPS before 1.4.4, as used on Apple Mac OS X 10.5.8, Mac OS X 10.6 before 10.6.4, and other platforms, allows remote attackers to hijack the authentication of administrators for requests that change settings.

Weakness

The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Mac_os_x Apple 10.5.8 (including) 10.5.8 (including)
Mac_os_x Apple 10.6.0 (including) 10.6.0 (including)
Mac_os_x Apple 10.6.1 (including) 10.6.1 (including)
Mac_os_x Apple 10.6.2 (including) 10.6.2 (including)
Mac_os_x Apple 10.6.3 (including) 10.6.3 (including)
Mac_os_x_server Apple 10.5.8 (including) 10.5.8 (including)
Mac_os_x_server Apple 10.6.0 (including) 10.6.0 (including)
Mac_os_x_server Apple 10.6.1 (including) 10.6.1 (including)
Mac_os_x_server Apple 10.6.2 (including) 10.6.2 (including)
Mac_os_x_server Apple 10.6.3 (including) 10.6.3 (including)
Red Hat Enterprise Linux 3 RedHat cups-1:1.1.17-13.3.65 *
Red Hat Enterprise Linux 4 RedHat cups-1:1.1.22-0.rc1.9.32.el4_8.6 *
Red Hat Enterprise Linux 5 RedHat cups-1:1.3.7-18.el5_5.4 *
Cups Ubuntu jaunty *
Cups Ubuntu karmic *
Cups Ubuntu lucid *
Cups Ubuntu upstream *
Cupsys Ubuntu dapper *
Cupsys Ubuntu hardy *
Cupsys 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 [REF-1482].
  • 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