CVE Vulnerabilities

CVE-2017-4928

Cross-Site Request Forgery (CSRF)

Published: Nov 17, 2017 | Modified: Oct 30, 2018
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
5 MEDIUM
AV:N/AC:L/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
Ubuntu

The flash-based vSphere Web Client (6.0 prior to 6.0 U3c and 5.5 prior to 5.5 U3f) i.e. not the new HTML5-based vSphere Client, contains SSRF and CRLF injection issues due to improper neutralization of URLs. An attacker may exploit these issues by sending a POST request with modified headers towards internal services leading to information disclosure.

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
Vcenter_server Vmware 5.5 (including) 5.5 (including)
Vcenter_server Vmware 5.5-1 (including) 5.5-1 (including)
Vcenter_server Vmware 5.5-1a (including) 5.5-1a (including)
Vcenter_server Vmware 5.5-1b (including) 5.5-1b (including)
Vcenter_server Vmware 5.5-1c (including) 5.5-1c (including)
Vcenter_server Vmware 5.5-2 (including) 5.5-2 (including)
Vcenter_server Vmware 5.5-2b (including) 5.5-2b (including)
Vcenter_server Vmware 5.5-2d (including) 5.5-2d (including)
Vcenter_server Vmware 5.5-2e (including) 5.5-2e (including)
Vcenter_server Vmware 5.5-3 (including) 5.5-3 (including)
Vcenter_server Vmware 5.5-3a (including) 5.5-3a (including)
Vcenter_server Vmware 5.5-3b (including) 5.5-3b (including)
Vcenter_server Vmware 5.5-3d (including) 5.5-3d (including)
Vcenter_server Vmware 5.5-3e (including) 5.5-3e (including)
Vcenter_server Vmware 5.5-b (including) 5.5-b (including)
Vcenter_server Vmware 5.5-c (including) 5.5-c (including)
Vcenter_server Vmware 6.0 (including) 6.0 (including)
Vcenter_server Vmware 6.0-1 (including) 6.0-1 (including)
Vcenter_server Vmware 6.0-1b (including) 6.0-1b (including)
Vcenter_server Vmware 6.0-2 (including) 6.0-2 (including)
Vcenter_server Vmware 6.0-2a (including) 6.0-2a (including)
Vcenter_server Vmware 6.0-2m (including) 6.0-2m (including)
Vcenter_server Vmware 6.0-3 (including) 6.0-3 (including)
Vcenter_server Vmware 6.0-3a (including) 6.0-3a (including)
Vcenter_server Vmware 6.0-3b (including) 6.0-3b (including)
Vcenter_server Vmware 6.0-a (including) 6.0-a (including)
Vcenter_server Vmware 6.0-b (including) 6.0-b (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