{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-7336 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-7336 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-7336 is a critical vulnerability in Fortinet, Inc. Fortinet FortiWLM, published on 22 Jul 2017. 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-7336 and fix it if it is affected.\n\nWhat it is: CVE-2017-7336 is a critical vulnerability in Fortinet, Inc. Fortinet FortiWLM, published on 22 Jul 2017. 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-7336 in the wild and no public exploit code.\n\nAffected product: Fortinet, Inc. Fortinet FortiWLM. 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-7336/ (Markdown: https://insights.sbomify.com/CVE-2017-7336/index.md)","id":"CVE-2017-7336","markdown":"https://insights.sbomify.com/CVE-2017-7336/index.md","name":"CVE-2017-7336","record":{"aliases":["GHSA-rj7f-vhqh-f6h9"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiWLM","requires_auth":"none","summary":"Remote attackers can log in using a hard-coded 'upgrade' account to execute commands with elevated privileges on FortiWLM systems.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortiwlm","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":"A hard-coded account named 'upgrade' in Fortinet FortiWLM 8.3.0 and lower versions allows a remote attacker to log-in and execute commands with 'upgrade' account privileges.","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 Fortinet FortiWLM","id":"CVE-2017-7336","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":"Missing authorization in Fortinet FortiPortal","id":"CVE-2017-7337"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-7335"},"products":["Fortinet FortiWLM"],"published":"2017-07-22","related":[{"cvss_score":9.6,"headline":"Path traversal in FortiWLM","id":"CVE-2023-34990","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":9.6,"headline":"Command injection in FortiWLM","id":"CVE-2023-34993","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":9.6,"headline":"Command injection in FortiWLM","id":"CVE-2023-36547","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":9.6,"headline":"Command injection in FortiWLM","id":"CVE-2023-36548","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":9.6,"headline":"Command injection in FortiWLM","id":"CVE-2023-36550","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":9.3,"headline":"SQL injection in FortiWLM","id":"CVE-2023-34991","kev_date_added":null,"published":"2023-11-14"}],"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":"Remote attackers can log in using a hard-coded 'upgrade' account to execute commands with elevated privileges on FortiWLM systems.","url":"https://insights.sbomify.com/CVE-2017-7336/"}