CVE-2016-8201: CSRF
First published: Sat Jan 14 2017(Updated: )
A CSRF vulnerability in Brocade Virtual Traffic Manager versions released prior to and including 11.0 could allow an attacker to trick a logged-in user into making administrative changes on the traffic manager cluster.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Brocade Virtual Traffic Manager | <=11.0 |
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-8201?
CVE-2016-8201 is classified as a medium-severity vulnerability.
How do I fix CVE-2016-8201?
To fix CVE-2016-8201, upgrade to Brocade Virtual Traffic Manager version 11.1 or later.
What types of attacks can CVE-2016-8201 facilitate?
CVE-2016-8201 can facilitate cross-site request forgery (CSRF) attacks leading to unauthorized administrative changes.
Which versions of Brocade Virtual Traffic Manager are affected by CVE-2016-8201?
Brocade Virtual Traffic Manager versions prior to and including 11.0 are affected by CVE-2016-8201.
Who is vulnerable to CVE-2016-8201?
Users of Brocade Virtual Traffic Manager who have not upgraded past version 11.0 are vulnerable to CVE-2016-8201.
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/author
- agent/softwarecombine
- agent/description
- agent/first-publish-date
- agent/event
- agent/tags
- agent/source
- vendor/brocade
- canonical/brocade virtual traffic manager
- version/brocade virtual traffic manager/11.0