First published: Fri Aug 11 2017(Updated: )
Fortinet FortiManager 5.0.x before 5.0.11, 5.2.x before 5.2.2 allows remote attackers to obtain arbitrary files via vectors involving another unspecified vulnerability.
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 | |
Fortinet FortiManager 2000E | ||
Fortinet FortiManager 200d | ||
Fortinet FortiManager | ||
Fortinet FortiManager 300E | ||
Fortinet FortiManager | ||
Fortinet FortiManager 400E |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-3614 has been classified with a medium severity level due to its potential to allow unauthorized file access.
To mitigate CVE-2015-3614, upgrade FortiManager to version 5.0.11 or later, or 5.2.2 or later.
CVE-2015-3614 affects FortiManager versions 5.0.0 through 5.0.10 and 5.2.0 through 5.2.1.
CVE-2015-3614 does not directly lead to remote code execution but allows attackers to access arbitrary files on the server.
Currently, the recommended solution for CVE-2015-3614 is to upgrade to the fixed versions, as no specific workaround has been provided.