| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in VMware NSX Edge up to 6.2.8/6.3.4. It has been rated as problematic. Affected is an unknown function. This manipulation causes cross site scripting. The identification of this vulnerability is CVE-2017-4929. It is possible to initiate the attack remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability has been found in VMware NSX Edge up to 6.2.8/6.3.4 and classified as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect confidentiality, and integrity. The summary by CVE is:
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.
The bug was discovered 11/16/2017. The weakness was shared 11/17/2017 (Website). The advisory is shared at vmware.com. This vulnerability is known as CVE-2017-4929 since 12/26/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $5k-$25k.
Upgrading to version 6.2.9 or 6.3.5 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 101891†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.vmware.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.6
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: NSX Edge 6.2.9/6.3.5
Timeline
12/26/2016 🔍11/16/2017 🔍
11/16/2017 🔍
11/17/2017 🔍
11/17/2017 🔍
11/18/2017 🔍
01/24/2021 🔍
Sources
Vendor: vmware.comAdvisory: vmware.com
Researcher: Jarad Kopf
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-4929 (🔍)
GCVE (CVE): GCVE-0-2017-4929
GCVE (VulDB): GCVE-100-109669
SecurityFocus: 101891 - VMware NSX Edge CVE-2017-4929 Cross site Scripting Vulnerability
SecurityTracker: 1039837
scip Labs: https://www.scip.ch/en/?labs.20060413
Entry
Created: 11/18/2017 09:00Updated: 01/24/2021 12:05
Changes: 11/18/2017 09:00 (59), 12/08/2019 14:17 (4), 01/24/2021 12:00 (2), 01/24/2021 12:05 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.