| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Fortinet FortiWLC. This impacts an unknown function. This manipulation causes hard-coded credentials. This vulnerability is tracked as CVE-2016-8491. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability has been found in Fortinet FortiWLC (the affected version is unknown) and classified as critical. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
The presence of a hardcoded account named 'core' in Fortinet FortiWLC allows attackers to gain unauthorized read/write access via a remote shell.
The bug was discovered 11/09/2016. The weakness was disclosed 02/01/2017 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2016-8491 since 10/07/2016. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1110.001 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 84 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 94186†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
License
Website
- Vendor: https://www.fortinet.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.2VulDB Meta Temp Score: 8.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
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
Class: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/07/2016 🔍11/09/2016 🔍
11/09/2016 🔍
02/01/2017 🔍
02/01/2017 🔍
02/02/2017 🔍
08/09/2020 🔍
Sources
Vendor: fortinet.comAdvisory: securityfocus.com⛔
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-8491 (🔍)
GCVE (CVE): GCVE-0-2016-8491
GCVE (VulDB): GCVE-100-96457
SecurityFocus: 94186 - FortiWLC CVE-2016-8491 Hardcoded Account Security Bypass Vulnerability
OSVDB: - CVE-2016-8491 - Fortinet - FortiWLC - Hardcoded Account Issue
Entry
Created: 02/02/2017 11:56Updated: 08/09/2020 20:27
Changes: 02/02/2017 11:56 (56), 08/09/2020 20:27 (6)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.