First published: Tue Aug 22 2017(Updated: )
Fortinet FortiManager 5.0 before 5.0.11 and 5.2 before 5.2.2 allow local users to gain privileges via crafted CLI commands.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Fortinet FortiManager | =5.0.0 | |
Fortinet FortiManager | =5.0.1 | |
Fortinet FortiManager | =5.0.2 | |
Fortinet FortiManager | =5.0.3 | |
Fortinet FortiManager | =5.0.4 | |
Fortinet FortiManager | =5.0.5 | |
Fortinet FortiManager | =5.0.6 | |
Fortinet FortiManager | =5.0.7 | |
Fortinet FortiManager | =5.0.8 | |
Fortinet FortiManager | =5.0.9 | |
Fortinet FortiManager | =5.0.10 | |
Fortinet FortiManager | =5.2.0 | |
Fortinet FortiManager | =5.2.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-3617 has a medium severity rating due to its potential to allow local users to escalate privileges.
To fix CVE-2015-3617, upgrade Fortinet FortiManager to version 5.0.11 or later, or version 5.2.2 or later.
CVE-2015-3617 impacts FortiManager versions 5.0.0 through 5.0.10 and 5.2.0 through 5.2.1.
CVE-2015-3617 can be exploited using crafted CLI commands by local users.
Temporary mitigation can include restricting local access to FortiManager until an upgrade is performed.