{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-7561 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-7561 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-7561 is a high-severity vulnerability in n/a, published on 5 Oct 2016. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-7561 and fix it if it is affected.\n\nWhat it is: CVE-2016-7561 is a high-severity vulnerability in n/a, published on 5 Oct 2016. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-7561 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-7561/ (Markdown: https://insights.sbomify.com/CVE-2016-7561/index.md)","id":"CVE-2016-7561","markdown":"https://insights.sbomify.com/CVE-2016-7561/index.md","name":"CVE-2016-7561","record":{"aliases":["GHSA-874w-4q4h-wg36"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiWLC","requires_auth":"high_privilege","summary":"Administrators can read sensitive user credentials from the pam.log file in Fortinet FortiWLC wireless controllers.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fortiwlc","vendor":"fortinet"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Fortinet FortiWLC 6.1-2-29 and earlier, 7.0-9-1, 7.0-10-0, 8.0-5-0, 8.1-2-0, and 8.2-4-0 allow administrators to obtain sensitive user credentials by reading the pam.log file.","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":"Information disclosure in n/a","id":"CVE-2016-7561","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-7562"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2016-7560"},"products":["n/a"],"published":"2016-10-05","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in FortiWLC","id":"CVE-2017-17539","kev_date_added":null,"published":"2018-05-07"},{"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"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Administrators can read sensitive user credentials from the pam.log file in Fortinet FortiWLC wireless controllers.","url":"https://insights.sbomify.com/CVE-2016-7561/"}