Fortinet FortiWan up to 4.2.4 diagnosis_control.php Username File improper authentication
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Fortinet FortiWan up to 4.2.4. This issue affects some unknown processing of the file diagnosis_control.php. Performing a manipulation of the argument Username as part of GET Request results in improper authentication (File). This vulnerability is identified as CVE-2016-4966. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as critical, was found in Fortinet FortiWan up to 4.2.4. This affects some unknown functionality of the file diagnosis_control.php. The manipulation of the argument UserName as part of a GET Request leads to a improper authentication vulnerability (File). CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:
The diagnosis_control.php page in Fortinet FortiWan (formerly AscernLink) before 4.2.5 allows remote authenticated users to download PCAP files via vectors related to the UserName GET parameter.
The weakness was released 09/21/2016 (Website). The advisory is shared at docs.fortinet.com. This vulnerability is uniquely identified as CVE-2016-4966 since 05/24/2016. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is required for exploitation. Technical details are known, but no exploit is available.
By approaching the search of inurl:diagnosis_control.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 4.2.5 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92781†). Entries connected to this vulnerability are available at VDB-91820, VDB-91822, VDB-91823 and VDB-91824. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.fortinet.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: FileClass: Improper authentication / File
CWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: FortiWan 4.2.5
Timeline
05/24/2016 🔍09/06/2016 🔍
09/21/2016 🔍
09/21/2016 🔍
09/22/2016 🔍
11/01/2024 🔍
Sources
Vendor: fortinet.comAdvisory: docs.fortinet.com
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-4966 (🔍)
GCVE (CVE): GCVE-0-2016-4966
GCVE (VulDB): GCVE-100-91821
CERT: 🔍
SecurityFocus: 92781 - Fortinet FortiWAN CVE-2016-4966 Authentication Bypass Vulnerability
See also: 🔍
Entry
Created: 09/22/2016 09:22Updated: 11/01/2024 01:32
Changes: 09/22/2016 09:22 (55), 04/22/2019 18:15 (12), 11/01/2024 01:32 (20)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.