CVE-2015-3614: Infoleak
Published 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.
Affected Software
19 affected components
Fortinet Fortimanager Firmware=5.0.0
Fortinet Fortimanager Firmware=5.0.1
Fortinet Fortimanager Firmware=5.0.2
Fortinet Fortimanager Firmware=5.0.3
Fortinet Fortimanager Firmware=5.0.4
Fortinet Fortimanager Firmware=5.0.5
Fortinet Fortimanager Firmware=5.0.6
Fortinet Fortimanager Firmware=5.0.7
Fortinet Fortimanager Firmware=5.0.8
Fortinet Fortimanager Firmware=5.0.9
Fortinet Fortimanager Firmware=5.0.10
Fortinet Fortimanager Firmware=5.2.0
Fortinet Fortimanager Firmware=5.2.1
Fortinet Fortimanager 2000e
Fortinet Fortimanager 200d
Fortinet Fortimanager 3000f
Fortinet Fortimanager 300e
Fortinet Fortimanager 3900e
Fortinet Fortimanager 400e
Event History
Aug 11, 2017
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2015-3614?
CVE-2015-3614 has been classified with a medium severity level due to its potential to allow unauthorized file access.
2
How do I fix CVE-2015-3614?
To mitigate CVE-2015-3614, upgrade FortiManager to version 5.0.11 or later, or 5.2.2 or later.
3
What versions of FortiManager are affected by CVE-2015-3614?
CVE-2015-3614 affects FortiManager versions 5.0.0 through 5.0.10 and 5.2.0 through 5.2.1.
4
Can CVE-2015-3614 lead to remote code execution?
CVE-2015-3614 does not directly lead to remote code execution but allows attackers to access arbitrary files on the server.
5
Is there a workaround for CVE-2015-3614?
Currently, the recommended solution for CVE-2015-3614 is to upgrade to the fixed versions, as no specific workaround has been provided.