CVE-2016-5336
First published: Wed Aug 31 2016(Updated: )
VMware vRealize Automation 7.0.x before 7.1 allows remote attackers to execute arbitrary code via unspecified vectors.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| VMware vRealize Automation | =7.0 | |
| VMware vRealize Automation | =7.0.1 |
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-5336?
The severity of CVE-2016-5336 is high due to its potential for remote code execution.
How do I fix CVE-2016-5336?
To fix CVE-2016-5336, upgrade VMware vRealize Automation to version 7.1 or later.
What versions are affected by CVE-2016-5336?
CVE-2016-5336 affects VMware vRealize Automation versions 7.0 and 7.0.1.
Can CVE-2016-5336 be exploited remotely?
Yes, CVE-2016-5336 can be exploited remotely, allowing attackers to execute arbitrary code.
Is there a patch available for CVE-2016-5336?
Yes, a patch for CVE-2016-5336 is included in VMware vRealize Automation version 7.1.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/remedy
- agent/references
- agent/last-modified-date
- agent/tags
- agent/severity
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- vendor/vmware
- canonical/vmware vrealize automation
- version/vmware vrealize automation/7.0
- version/vmware vrealize automation/7.0.1