{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-9606 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9606 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-9606 is a high-severity vulnerability in n/a, published on 15 Jun 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-9606 and fix it if it is affected.\n\nWhat it is: CVE-2017-9606 is a high-severity vulnerability in n/a, published on 15 Jun 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-9606 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-2017-9606/ (Markdown: https://insights.sbomify.com/CVE-2017-9606/index.md)","id":"CVE-2017-9606","markdown":"https://insights.sbomify.com/CVE-2017-9606/index.md","name":"CVE-2017-9606","record":{"aliases":["GHSA-6vwh-f528-jv49"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ViPNet Client","requires_auth":"low_privilege","summary":"Local attackers can gain privileges by placing a malicious update file in the update folder due to insecure permissions and missing integrity checks.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vipnet_client","vendor":"infotecs"},{"product":"vipnet_coordinator","vendor":"infotecs"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-354","name":"Improper Validation of Integrity Check Value"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Infotecs ViPNet Client and Coordinator before 4.3.2-42442 allow local users to gain privileges by placing a Trojan horse ViPNet update file in the update folder. The attack succeeds because of incorrect folder permissions in conjunction with a lack of integrity and authenticity checks.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2017-06-14","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-06-14T04:30:36Z","kind":"github_poc","ref":"https://github.com/Houl777/CVE-2017-9606","stars":0,"title":null}],"tier":"poc_unverified"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2017-9606","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Integer overflow in n/a","id":"CVE-2017-9607"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2017-9605"},"products":["n/a"],"published":"2017-06-15","related":[{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2013-3496","kev_date_added":null,"published":"2013-05-22"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Local attackers can gain privileges by placing a malicious update file in the update folder due to insecure permissions and missing integrity checks.","url":"https://insights.sbomify.com/CVE-2017-9606/"}