# CVE-2017-4929: Cross-site scripting in NSX Edge

> Cross-Site Scripting in VMware NSX Edge allows attackers to disclose sensitive information via malicious scripts.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qvjc-9gm9-g5qq

## What is CVE-2017-4929?

CVE-2017-4929 is a medium-severity cross-site scripting vulnerability in VMware NSX Edge, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

VMware NSX Edge (6.2.x before 6.2.9 and 6.3.x before 6.3.5) contains a moderate Cross-Site Scripting (XSS) issue which may lead to information disclosure.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Vmware Nsx Edge.

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

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

## Is CVE-2017-4929 being exploited?

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

## Other vulnerabilities in VMware NSX Edge

- [CVE-2016-2079](https://insights.sbomify.com/CVE-2016-2079/): Information disclosure in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-4929 is a medium-severity cross-site scripting vulnerability in VMware NSX Edge, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-4929 in the wild and no public exploit code.

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

## Sources

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

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