{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-3130 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-3130 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-3130 is a high-severity vulnerability in Fortinet Fortios, published on 10 Aug 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-3130 and fix it if it is affected.\n\nWhat it is: CVE-2017-3130 is a high-severity vulnerability in Fortinet Fortios, published on 10 Aug 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-3130 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortios. 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-3130/ (Markdown: https://insights.sbomify.com/CVE-2017-3130/index.md)","id":"CVE-2017-3130","markdown":"https://insights.sbomify.com/CVE-2017-3130/index.md","name":"CVE-2017-3130","record":{"aliases":["GHSA-m2hm-m569-8xqm"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiOS","requires_auth":"none","summary":"Attackers can obtain FortiOS version information by inspecting IKE VendorID packets, potentially aiding targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortios","vendor":"fortinet"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"An information disclosure vulnerability in Fortinet FortiOS 5.6.0, 5.4.4 and below versions allows attacker to get FortiOS version info by inspecting FortiOS IKE VendorID packets.","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 Fortinet FortiOS","id":"CVE-2017-3130","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortios","products":["fortinet:fortios"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in Fortinet FortiOS","id":"CVE-2017-3131"},"packages":[],"prev":{"headline":"Cross-site scripting in Fortinet FortiWeb","id":"CVE-2017-3129"},"products":["Fortinet FortiOS"],"published":"2017-08-10","related":[{"cvss_score":9.8,"headline":"Fortinet Multiple Products Format String","id":"CVE-2024-23113","kev_date_added":"2024-10-09","published":"2024-02-15"},{"cvss_score":9.8,"headline":"Fortinet Multiple Products Authentication Bypass","id":"CVE-2022-40684","kev_date_added":"2022-10-11","published":"2022-10-18"},{"cvss_score":9.6,"headline":"Fortinet FortiOS and FortiProxy Authentication Bypass","id":"CVE-2024-55591","kev_date_added":"2025-01-14","published":"2025-01-14"},{"cvss_score":9.6,"headline":"Fortinet FortiOS Out-of-Bound Write","id":"CVE-2024-21762","kev_date_added":"2024-02-09","published":"2024-02-09"},{"cvss_score":9.3,"headline":"Fortinet FortiOS Heap-Based Buffer Overflow","id":"CVE-2022-42475","kev_date_added":"2022-12-13","published":"2023-01-02"},{"cvss_score":9.2,"headline":"Fortinet FortiOS and FortiProxy SSL-VPN Heap-Based Buffer Overflow","id":"CVE-2023-27997","kev_date_added":"2023-06-13","published":"2023-06-13"},{"cvss_score":9.1,"headline":"Fortinet Multiple Products Improper Verification of Cryptographic Signature","id":"CVE-2025-59718","kev_date_added":"2025-12-16","published":"2025-12-09"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-10-25","vendors":["Fortinet, Inc."]},"summary":"Attackers can obtain FortiOS version information by inspecting IKE VendorID packets, potentially aiding targeted attacks.","url":"https://insights.sbomify.com/CVE-2017-3130/"}