{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16777 exists.","fix":"No fix has been published for CVE-2017-16777 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-16777 is a high-severity vulnerability in n/a, published on 16 Nov 2017. 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-16777 and fix it if it is affected.\n\nWhat it is: CVE-2017-16777 is a high-severity vulnerability in n/a, published on 16 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-16777 exists.\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-16777/ (Markdown: https://insights.sbomify.com/CVE-2017-16777/index.md)","id":"CVE-2017-16777","markdown":"https://insights.sbomify.com/CVE-2017-16777/index.md","name":"CVE-2017-16777","record":{"aliases":["GHSA-fgv7-f23j-2rj6"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Vagrant VMware plugin","requires_auth":"low_privilege","summary":"A local attacker can escalate to root by exploiting a SUID helper in the Vagrant VMware Fusion plugin when the underlying software is missing.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vagrant","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":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"If HashiCorp Vagrant VMware Fusion plugin (aka vagrant-vmware-fusion) 5.0.3 is installed but VMware Fusion is not, a local attacker can create a fake application directory and exploit the suid sudo helper in order to escalate to root.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2017-12-06","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2017-12-06","kind":"exploitdb","ref":"43219","stars":null,"title":"Hashicorp vagrant-vmware-fusion 5.0.3 - Local Privilege Escalation"}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2017-16777","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Auth bypass in n/a","id":"CVE-2017-16778"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2017-16776"},"products":["n/a"],"published":"2017-11-16","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-42717","kev_date_added":null,"published":"2022-10-11"},{"cvss_score":7.8,"headline":"Race condition in n/a","id":"CVE-2017-16001","kev_date_added":null,"published":"2017-11-06"},{"cvss_score":3.8,"headline":"Vagrant’s Windows Installer Allowed Directory Junction Write","id":"CVE-2023-5834","kev_date_added":null,"published":"2023-10-27"}],"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":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"A local attacker can escalate to root by exploiting a SUID helper in the Vagrant VMware Fusion plugin when the underlying software is missing.","url":"https://insights.sbomify.com/CVE-2017-16777/"}