{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-8495 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-8495 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-8495 is a high-severity vulnerability in Fortinet FortiManager, published on 13 Feb 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-2016-8495 and fix it if it is affected.\n\nWhat it is: CVE-2016-8495 is a high-severity vulnerability in Fortinet FortiManager, published on 13 Feb 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-2016-8495 in the wild and no public exploit code.\n\nAffected product: Fortinet FortiManager. 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-8495/ (Markdown: https://insights.sbomify.com/CVE-2016-8495/index.md)","id":"CVE-2016-8495","markdown":"https://insights.sbomify.com/CVE-2016-8495/index.md","name":"CVE-2016-8495","record":{"aliases":["GHSA-vq5h-hrvh-ff3m"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiManager","requires_auth":"none","summary":"Remote attackers can bypass certificate validation via MITM attacks on FortiManager, potentially spoofing trusted entities.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortimanager_firmware","vendor":"fortinet"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An improper certificate validation vulnerability in Fortinet FortiManager 5.0.6 through 5.2.7 and 5.4.0 through 5.4.1 allows remote attacker to spoof a trusted entity by using a man-in-the-middle (MITM) attack via the Fortisandbox devices probing feature.","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":"Security feature bypass in FortiManager","id":"CVE-2016-8495","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-8496"},"packages":[],"prev":{"headline":"File upload in Fortinet Connect","id":"CVE-2016-8494"},"products":["FortiManager"],"published":"2017-02-13","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2015-3616","kev_date_added":null,"published":"2017-08-11"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-3617","kev_date_added":null,"published":"2017-08-22"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2015-3614","kev_date_added":null,"published":"2017-08-11"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2015-3615","kev_date_added":null,"published":"2017-08-11"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2015-8037","kev_date_added":null,"published":"2015-11-02"},{"cvss_score":4.3,"headline":"Cross-site scripting in n/a","id":"CVE-2015-8038","kev_date_added":null,"published":"2015-11-02"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-25","vendors":["Fortinet"]},"summary":"Remote attackers can bypass certificate validation via MITM attacks on FortiManager, potentially spoofing trusted entities.","url":"https://insights.sbomify.com/CVE-2016-8495/"}