# CVE-2017-4952: Auth bypass in VMware Xenon

> An attacker can bypass authentication on utility endpoints to access sensitive information in VMware Xenon.

- **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:** 2 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rmq6-x837-659x

## What is CVE-2017-4952?

CVE-2017-4952 is a high-severity authentication bypass vulnerability in VMware Xenon, published on 2 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VMware Xenon 1.x, prior to 1.5.4-CR7_1, 1.5.7_7, 1.5.4-CR6_2, 1.3.7-CR1_2, 1.1.0-CR0-3, 1.1.0-CR3_1,1.4.2-CR4_1, and 1.5.4_8, contains an authentication bypass vulnerability due to insufficient access controls for utility endpoints. Successful exploitation of this issue may result in information disclosure.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Vmware Xenon.

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

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

## Is CVE-2017-4952 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-4952 is a high-severity authentication bypass vulnerability in VMware Xenon, published on 2 May 2018. 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-4952 in the wild and no public exploit code.

Affected product: VMware Xenon. 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-4952/ (Markdown: https://insights.sbomify.com/CVE-2017-4952/index.md)
```

## Sources

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

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