{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11193 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11193 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-11193 is a high-severity vulnerability in Pulsesecure Pulse Connect Secure, published on 12 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-11193 and fix it if it is affected.\n\nWhat it is: CVE-2017-11193 is a high-severity vulnerability in Pulsesecure Pulse Connect Secure, published on 12 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-11193 in the wild and no public exploit code.\n\nAffected product: Pulsesecure Pulse Connect Secure. 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-11193/ (Markdown: https://insights.sbomify.com/CVE-2017-11193/index.md)","id":"CVE-2017-11193","markdown":"https://insights.sbomify.com/CVE-2017-11193/index.md","name":"CVE-2017-11193","record":{"aliases":["GHSA-c6vq-95h3-7xfg"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Pulse Connect Secure","requires_auth":"none","summary":"An attacker can force an admin to execute network diagnostic commands via CSRF, potentially leading to command execution or security bypass.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pulse_connect_secure","vendor":"pulsesecure"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Pulse Connect Secure 8.3R1 has CSRF in diag.cgi. In the panel, the diag.cgi file is responsible for running commands such as ping, ping6, traceroute, traceroute6, nslookup, arp, and Portprobe. These functions do not have any protections against CSRF. That can allow an attacker to run these commands against any IP if they can get an admin to visit their malicious CSRF page.","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":"Cross-site request forgery in n/a","id":"CVE-2017-11193","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"pulsesecure:pulse_connect_secure","products":["pulsesecure:pulse_connect_secure"],"type":"csrf","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-11194"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2017-11191"},"products":["n/a"],"published":"2017-07-12","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-5299","kev_date_added":null,"published":"2018-01-16"},{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2020-11580","kev_date_added":null,"published":"2020-04-06"},{"cvss_score":8.8,"headline":"Other in n/a","id":"CVE-2020-11582","kev_date_added":null,"published":"2020-04-06"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2017-11196","kev_date_added":null,"published":"2017-07-12"},{"cvss_score":8.1,"headline":"Command injection in n/a","id":"CVE-2020-11581","kev_date_added":null,"published":"2020-04-06"},{"cvss_score":6.5,"headline":"Auth bypass in n/a","id":"CVE-2016-3985","kev_date_added":null,"published":"2016-04-08"}],"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-05","vendors":["n/a"]},"summary":"An attacker can force an admin to execute network diagnostic commands via CSRF, potentially leading to command execution or security bypass.","url":"https://insights.sbomify.com/CVE-2017-11193/"}