CVE-2017-4952 json
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 a…
published 2018-05-02 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-14069
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.7%
- EPSS 3.7% chance of exploitation in 30 days, percentile 89%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- github.com/vmware/xenon@b1fd306 commit
- github.com/vmware/xenon@30ae41b commit
- github.com/vmware/xenon@756d893 commit
- github.com/vmware/xenon@5682ef8 commit
- github.com/vmware/xenon@ec30db9 commit
- github.com/vmware/xenon@055ae13 commit
- github.com/vmware/xenon@c23964e commit
- github.com/vmware/xenon@7a747d8 commit
- github.com/vmware/xenon@06b9947 commit
Exploit prediction
3.73% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- VMware VMware Xenon
Classification
- Weakness
-
- CWE-732 Incorrect Permission Assignment for Critical Resource
References
-
github.com
/vmware/xenon/commit/b1fd306047ecdac82661d636ebee801a7f2b3a0a
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/30ae41bccf418d88b52b35a81efb3c1304b798f8
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/756d893573414eec8635c2aba2345c4dcf10b21c
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/5682ef8d40569afd00fb9a5933e7706bb5b66713
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/ec30db9afada9cb52852082ce4d7d0095524f3b3
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/055ae13603f0cc3cd7cf59f20ce314bf8db583e1
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/c23964eb57e846126daef98ef7ed15400313e977
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/7a747d82b80cd38d2c11a0d9cdedb71c722a2c75
patch, third-party-advisory
-
github.com
/vmware/xenon/commit/06b9947cf603ba40fd8b03bfeb2e84528a7ab592
patch, third-party-advisory
-
securityfocus.com
/bid/103093
vdb-entry, third-party-advisory
-
seclists.org
/oss-sec/2018/q1/153
mailing-list, third-party-advisory
Sources
- CVE List CVE-2017-4952
- NVD CVE-2017-4952
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.