{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-16873 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-16873 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16873 is a high-severity vulnerability in n/a, published on 29 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-16873 and fix it if it is affected.\n\nWhat it is: CVE-2017-16873 is a high-severity vulnerability in n/a, published on 29 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-16873 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-16873/ (Markdown: https://insights.sbomify.com/CVE-2017-16873/index.md)","id":"CVE-2017-16873","markdown":"https://insights.sbomify.com/CVE-2017-16873/index.md","name":"CVE-2017-16873","record":{"aliases":["GHSA-v2px-fp32-982g"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vagrant VMware Fusion plugin","requires_auth":"low_privilege","summary":"Attackers can exploit an unsanitized PATH in the suid binary to escalate privileges to root on systems using the Vagrant VMware Fusion plugin.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vagrant_vmware_fusion","vendor":"hashicorp"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"description":"It is possible to exploit an unsanitized PATH in the suid binary that ships with vagrant-vmware-fusion 4.0.25 through 5.0.4 in order to escalate to root privileges.","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":"Privilege escalation in n/a","id":"CVE-2017-16873","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-16875"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2017-16872"},"products":["n/a"],"published":"2018-03-29","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-11741","kev_date_added":null,"published":"2017-08-08"},{"cvss_score":7.8,"headline":"Race condition in n/a","id":"CVE-2017-16512","kev_date_added":null,"published":"2018-03-29"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-12579","kev_date_added":null,"published":"2017-10-19"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-7642","kev_date_added":null,"published":"2017-08-02"},{"cvss_score":7,"headline":"Privilege escalation in n/a","id":"CVE-2017-16839","kev_date_added":null,"published":"2018-03-29"},{"cvss_score":7,"headline":"Race condition in n/a","id":"CVE-2017-15884","kev_date_added":null,"published":"2017-10-31"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can exploit an unsanitized PATH in the suid binary to escalate privileges to root on systems using the Vagrant VMware Fusion plugin.","url":"https://insights.sbomify.com/CVE-2017-16873/"}