CVE Vulnerabilities

CVE-2012-1843

Cross-Site Request Forgery (CSRF)

Published: Mar 22, 2012 | Modified: Jan 10, 2018
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
RedHat/V3
Ubuntu

Cross-site request forgery (CSRF) vulnerability in saveRestore.htm on the Quantum Scalar i500 tape library with firmware before i7.0.3 (604G.GS00100), also distributed as the Dell ML6000 tape library with firmware before A20-00 (590G.GS00100), allows remote attackers to hijack the authentication of users for requests that execute Linux commands via the fileName parameter, related to a command-injection vulnerability.

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
Scalar_i500_firmware Quantum * i7.0.2 (including)
Scalar_i500_firmware Quantum i2 (including) i2 (including)
Scalar_i500_firmware Quantum i3 (including) i3 (including)
Scalar_i500_firmware Quantum i3.1 (including) i3.1 (including)
Scalar_i500_firmware Quantum i4 (including) i4 (including)
Scalar_i500_firmware Quantum i5 (including) i5 (including)
Scalar_i500_firmware Quantum i5.1 (including) i5.1 (including)
Scalar_i500_firmware Quantum i6 (including) i6 (including)
Scalar_i500_firmware Quantum i6.1 (including) i6.1 (including)
Scalar_i500_firmware Quantum i7 (including) i7 (including)
Scalar_i500_firmware Quantum i7.0.1 (including) i7.0.1 (including)
Scalar_i500_firmware Quantum sp4 (including) sp4 (including)
Scalar_i500_firmware Quantum sp4.2 (including) sp4.2 (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