CVE-2017-17540
First published: Mon May 07 2018(Updated: )
The presence of a hardcoded account in Fortinet FortiWLC 8.3.3 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<=7.0.11 | |
| Fortinet FortiWLC | >=8.0<=8.3.3 |
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-2017-17540?
CVE-2017-17540 has a medium severity due to the potential for unauthorized access to sensitive information and system controls.
How do I fix CVE-2017-17540?
To fix CVE-2017-17540, update the Fortinet FortiWLC to a version beyond 8.3.3 or apply the recommended patches from Fortinet.
What types of access does CVE-2017-17540 allow?
CVE-2017-17540 allows attackers to gain unauthorized read/write access via a remote shell.
Which versions of Fortinet FortiWLC are affected by CVE-2017-17540?
CVE-2017-17540 affects Fortinet FortiWLC versions from 7.0 to 8.3.3 inclusive.
Who can be impacted by CVE-2017-17540?
Any organization using vulnerable versions of Fortinet FortiWLC could be impacted by CVE-2017-17540 due to the risk of unauthorized access.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- agent/author
- agent/severity
- agent/weakness
- agent/tags
- agent/description
- agent/event
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- vendor/fortinet
- canonical/fortinet fortiwlc
- version/fortinet fortiwlc/7.0
- version/fortinet fortiwlc/7.0.11
- version/fortinet fortiwlc/8.0
- version/fortinet fortiwlc/8.3.3