CVE-2016-8491
First published: Wed Feb 01 2017(Updated: )
The presence of a hardcoded account named 'core' in Fortinet FortiWLC allows attackers to gain unauthorized read/write access via a remote shell.
Credit: psirt@fortinet.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Fortinet FortiWLC | =7.0-9-1 | |
| Fortinet FortiWLC | =7.0-10-0 | |
| Fortinet FortiWLC | =8.1-2-0 | |
| Fortinet FortiWLC | =8.1-3-2 | |
| Fortinet FortiWLC | =8.2-4-0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2016-8491?
CVE-2016-8491 is considered critical due to the existence of a hardcoded account that can lead to unauthorized access.
How do I fix CVE-2016-8491?
To mitigate CVE-2016-8491, users should upgrade Fortinet FortiWLC to a patched version that removes the hardcoded account.
Which versions are affected by CVE-2016-8491?
CVE-2016-8491 affects Fortinet FortiWLC versions 7.0-9-1, 7.0-10-0, 8.1-2-0, 8.1-3-2, and 8.2-4-0.
What are the risks associated with CVE-2016-8491?
The risks of CVE-2016-8491 include potential unauthorized read/write access to sensitive information and system control.
Is there a workaround for CVE-2016-8491?
There are no specific workarounds for CVE-2016-8491; upgrading to a secure version is the recommended solution.
- collector/nvd-index
- agent/references
- agent/softwarecombine
- agent/author
- agent/severity
- agent/weakness
- agent/type
- agent/description
- agent/event
- agent/first-publish-date
- agent/tags
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- vendor/fortinet
- canonical/fortinet fortiwlc
- version/fortinet fortiwlc/7.0-9-1
- version/fortinet fortiwlc/7.0-10-0
- version/fortinet fortiwlc/8.1-2-0
- version/fortinet fortiwlc/8.1-3-2
- version/fortinet fortiwlc/8.2-4-0