{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-17539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-17539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-17539 is a critical vulnerability in Fortinet, Inc. FortiWLC, published on 7 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-17539 and fix it if it is affected.\n\nWhat it is: CVE-2017-17539 is a critical vulnerability in Fortinet, Inc. FortiWLC, published on 7 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-17539 in the wild and no public exploit code.\n\nAffected product: Fortinet, Inc. FortiWLC. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-17539/ (Markdown: https://insights.sbomify.com/CVE-2017-17539/index.md)","id":"CVE-2017-17539","markdown":"https://insights.sbomify.com/CVE-2017-17539/index.md","name":"CVE-2017-17539","record":{"aliases":["GHSA-fwcv-cv48-wpq2"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiWLC","requires_auth":"none","summary":"Attackers can gain unauthorized read/write access via a remote shell due to a hardcoded account in Fortinet FortiWLC.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortiwlc","vendor":"fortinet"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"The presence of a hardcoded account in Fortinet FortiWLC 7.0.11 and earlier allows attackers to gain unauthorized read/write access via a remote shell.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in FortiWLC","id":"CVE-2017-17539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in FortiWLC","id":"CVE-2017-17540"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2017-17538"},"products":["FortiWLC"],"published":"2018-05-07","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in FortiWLC","id":"CVE-2017-17540","kev_date_added":null,"published":"2018-05-07"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2016-7560","kev_date_added":null,"published":"2016-10-05"},{"cvss_score":9.1,"headline":"Hardcoded credentials in Fortinet FortiWLC","id":"CVE-2016-8491","kev_date_added":null,"published":"2017-02-01"},{"cvss_score":8.8,"headline":"Privilege escalation in Fortinet FortiWLC","id":"CVE-2021-42758","kev_date_added":null,"published":"2021-12-08"},{"cvss_score":7.2,"headline":"Command injection in n/a","id":"CVE-2017-7341","kev_date_added":null,"published":"2017-10-26"},{"cvss_score":7.2,"headline":"Information disclosure in n/a","id":"CVE-2016-7561","kev_date_added":null,"published":"2016-10-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-25","vendors":["Fortinet, Inc."]},"summary":"Attackers can gain unauthorized read/write access via a remote shell due to a hardcoded account in Fortinet FortiWLC.","url":"https://insights.sbomify.com/CVE-2017-17539/"}