CVE-2016-7456
First published: Thu Dec 29 2016(Updated: )
VMware vSphere Data Protection (VDP) 5.5.x though 6.1.x has an SSH private key with a publicly known password, which makes it easier for remote attackers to obtain login access via an SSH session.
Credit: security@vmware.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| VMware vSphere Data Protection | =5.5.1 | |
| VMware vSphere Data Protection | =5.5.5 | |
| VMware vSphere Data Protection | =5.5.6 | |
| VMware vSphere Data Protection | =5.5.7 | |
| VMware vSphere Data Protection | =5.5.8 | |
| VMware vSphere Data Protection | =5.5.9 | |
| VMware vSphere Data Protection | =5.5.10 | |
| VMware vSphere Data Protection | =5.5.11 | |
| VMware vSphere Data Protection | =5.8.0 | |
| VMware vSphere Data Protection | =5.8.1 | |
| VMware vSphere Data Protection | =5.8.2 | |
| VMware vSphere Data Protection | =5.8.3 | |
| VMware vSphere Data Protection | =5.8.4 | |
| VMware vSphere Data Protection | =6.0.0 | |
| VMware vSphere Data Protection | =6.0.1 | |
| VMware vSphere Data Protection | =6.0.2 | |
| VMware vSphere Data Protection | =6.0.3 | |
| VMware vSphere Data Protection | =6.0.4 | |
| VMware vSphere Data Protection | =6.1.0 | |
| VMware vSphere Data Protection | =6.1.1 | |
| VMware vSphere Data Protection | =6.1.2 | |
| VMware vSphere Data Protection | =6.1.3 |
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-2016-7456?
CVE-2016-7456 is considered to have a high severity due to the risk of unauthorized SSH access.
How do I fix CVE-2016-7456?
To fix CVE-2016-7456, update your VMware vSphere Data Protection to a version not affected by this vulnerability.
What versions are affected by CVE-2016-7456?
CVE-2016-7456 affects VMware vSphere Data Protection versions 5.5.x through 6.1.x.
Can CVE-2016-7456 be exploited remotely?
Yes, CVE-2016-7456 can be exploited remotely through an SSH session.
Is there a workaround for CVE-2016-7456?
While the best solution is to apply updates, limiting SSH access can be a temporary workaround for CVE-2016-7456.
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/references
- agent/weakness
- agent/last-modified-date
- agent/softwarecombine
- agent/description
- agent/first-publish-date
- agent/event
- agent/tags
- agent/source
- vendor/vmware
- canonical/vmware vsphere data protection
- version/vmware vsphere data protection/5.5.1
- version/vmware vsphere data protection/5.5.5
- version/vmware vsphere data protection/5.5.6
- version/vmware vsphere data protection/5.5.7
- version/vmware vsphere data protection/5.5.8
- version/vmware vsphere data protection/5.5.9
- version/vmware vsphere data protection/5.5.10
- version/vmware vsphere data protection/5.5.11
- version/vmware vsphere data protection/5.8.0
- version/vmware vsphere data protection/5.8.1
- version/vmware vsphere data protection/5.8.2
- version/vmware vsphere data protection/5.8.3
- version/vmware vsphere data protection/5.8.4
- version/vmware vsphere data protection/6.0.0
- version/vmware vsphere data protection/6.0.1
- version/vmware vsphere data protection/6.0.2
- version/vmware vsphere data protection/6.0.3
- version/vmware vsphere data protection/6.0.4
- version/vmware vsphere data protection/6.1.0
- version/vmware vsphere data protection/6.1.1
- version/vmware vsphere data protection/6.1.2
- version/vmware vsphere data protection/6.1.3