CVE-2017-4921
First published: Tue Aug 01 2017(Updated: )
VMware vCenter Server (6.5 prior to 6.5 U1) contains an insecure library loading issue that occurs due to the use of LD_LIBRARY_PATH variable in an unsafe manner. Successful exploitation of this issue may allow unprivileged host users to load a shared library that may lead to privilege escalation.
Credit: security@vmware.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| VMware vCenter | =6.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2017-4921?
CVE-2017-4921 is classified as a high severity vulnerability due to its potential to allow privilege escalation.
How do I fix CVE-2017-4921?
To fix CVE-2017-4921, upgrade VMware vCenter Server to version 6.5 U1 or later.
Who is affected by CVE-2017-4921?
CVE-2017-4921 affects VMware vCenter Server version 6.5 prior to 6.5 U1.
What kind of attack can be executed using CVE-2017-4921?
Exploitation of CVE-2017-4921 can lead to unauthorized privilege escalation by unprivileged host users.
Is CVE-2017-4921 a local or remote vulnerability?
CVE-2017-4921 is a local privilege escalation vulnerability.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/remedy
- agent/last-modified-date
- agent/author
- agent/references
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/vmware
- canonical/vmware vcenter
- version/vmware vcenter/6.5