{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-42717 in the wild and no public exploit code.","fix":"Change a configuration setting.","what":"CVE-2022-42717 is a high-severity vulnerability in n/a, published on 11 Oct 2022. 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-2022-42717 and fix it if it is affected.\n\nWhat it is: CVE-2022-42717 is a high-severity vulnerability in n/a, published on 11 Oct 2022. 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-2022-42717 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-2022-42717/ (Markdown: https://insights.sbomify.com/CVE-2022-42717/index.md)","id":"CVE-2022-42717","markdown":"https://insights.sbomify.com/CVE-2022-42717/index.md","name":"CVE-2022-42717","record":{"aliases":["AZL-11115","GHSA-mc87-5qgf-5qvj","UBUNTU-CVE-2022-42717"],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"HashiCorp Packer","requires_auth":"low_privilege","summary":"Non-privileged users can execute arbitrary commands as root if the host uses the insecure recommended sudoers configuration for Vagrant.","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":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"An issue was discovered in Hashicorp Packer before 2.3.1. The recommended sudoers configuration for Vagrant on Linux is insecure. If the host has been configured according to this documentation, non-privileged users on the host can leverage a wildcard in the sudoers configuration to execute arbitrary commands as root.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Privilege escalation in n/a","id":"CVE-2022-42717","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2022-42718"},"packages":[],"prev":{"headline":"Use after free in n/a","id":"CVE-2022-42716"},"products":["n/a"],"published":"2022-10-11","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-16777","kev_date_added":null,"published":"2017-11-16"},{"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)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-20","vendors":["n/a"]},"summary":"Non-privileged users can execute arbitrary commands as root if the host uses the insecure recommended sudoers configuration for Vagrant.","url":"https://insights.sbomify.com/CVE-2022-42717/"}