# CVE-2017-4928: Server-side request forgery in vSphere Web Client

> An attacker can exploit SSRF and CRLF injection in the vSphere Web Client to access internal services and disclose sensitive information.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hgcm-2jjw-4pr2

## What is CVE-2017-4928?

CVE-2017-4928 is a high-severity server-side request forgery vulnerability in Vmware Vcenter Server, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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: CWE-918 (Server-Side Request Forgery), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-4928?

It affects 1 product.


Products: Vmware Vcenter Server.

## How do I fix CVE-2017-4928?

No fix has been published for CVE-2017-4928 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-4928 being exploited?

There is no known exploitation of CVE-2017-4928 in the wild and no public exploit code.

## Other vulnerabilities in Vmware Vcenter Server

- [CVE-2026-59310](https://insights.sbomify.com/CVE-2026-59310/): Broadcom VMware vCenter Path Traversal (critical 9.8, exploited in the wild)
- [CVE-2023-34048](https://insights.sbomify.com/CVE-2023-34048/): VMware vCenter Server Out-of-Bounds Write (critical 9.8, exploited in the wild)
- [CVE-2020-3952](https://insights.sbomify.com/CVE-2020-3952/): VMware vCenter Server Information Disclosure (critical 9.8, exploited in the wild)
- [CVE-2021-22017](https://insights.sbomify.com/CVE-2021-22017/): VMware vCenter Server Improper Access Control (medium 5.3, exploited in the wild)
- [CVE-2015-2342](https://insights.sbomify.com/CVE-2015-2342/): Code injection in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-4928 and fix it if it is affected.

What it is: CVE-2017-4928 is a high-severity server-side request forgery vulnerability in Vmware Vcenter Server, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-4928 in the wild and no public exploit code.

Affected product: Vmware Vcenter Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-4928/ (Markdown: https://insights.sbomify.com/CVE-2017-4928/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-4928
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-4928
- OSV: https://osv.dev/vulnerability/CVE-2017-4928

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-4928/
Summaries are generated and may contain mistakes; the official description above is the record.