{"answers":{"affected":"2 open source packages ship an affected version, including github.com/hashicorp/vagrant. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-5834 in the wild and no public exploit code.","fix":"Upgrade github.com/hashicorp/vagrant to 2.4.0 or later.","what":"CVE-2023-5834 is a low-severity path traversal vulnerability in HashiCorp Vagrant, published on 27 Oct 2023. 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-2023-5834 and fix it if it is affected.\n\nWhat it is: CVE-2023-5834 is a low-severity path traversal vulnerability in HashiCorp Vagrant, published on 27 Oct 2023. 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-2023-5834 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/hashicorp/vagrant (Go): affected all versions; fixed in 2.4.0\n- github.com/hashicorp/vagrant (Go): affected all versions; fixed in 2.4.0\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-2023-5834/ (Markdown: https://insights.sbomify.com/CVE-2023-5834/index.md)","id":"CVE-2023-5834","markdown":"https://insights.sbomify.com/CVE-2023-5834/index.md","name":"CVE-2023-5834","record":{"aliases":["GHSA-47xw-vw6m-w9fq"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Vagrant Windows installer","requires_auth":"low_privilege","summary":"Attackers can exploit directory junctions in the Windows installer to perform unauthorized file system writes, potentially leading to privilege escalation or code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[{"product":"vagrant","vendor":"hashicorp"}],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"},{"id":"CWE-1386","name":"Insecure Operation on Windows Junction / Mount Point"}],"description":"HashiCorp Vagrant's Windows installer targeted a custom location with a non-protected path that could be junctioned, introducing potential for unauthorized file system writes. Fixed in Vagrant 2.4.0.","ecosystems":["Go"],"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":"Vagrant’s Windows Installer Allowed Directory Junction Write","id":"CVE-2023-5834","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"path_traversal","year":"2023"},"n_packages":2,"n_references":1,"next":{"headline":"hu60t hu60wap6 ubbparser.php markdown cross site scripting","id":"CVE-2023-5835"},"packages":[{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vagrant","purl":null,"source":"GHSA-47xw-vw6m-w9fq"},{"ecosystem":"Go","fixed":["2.4.0"],"introduced":["0"],"last_affected":[],"package":"github.com/hashicorp/vagrant","purl":"pkg:golang/github.com/hashicorp/vagrant","source":"GHSA-47xw-vw6m-w9fq"}],"prev":{"headline":"Improper Access Control in mintplex-labs/anything-llm","id":"CVE-2023-5833"},"products":["Vagrant"],"published":"2023-10-27","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":"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"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"partial"},"state":"PUBLISHED","updated":"2024-09-09","vendors":["HashiCorp"]},"summary":"Attackers can exploit directory junctions in the Windows installer to perform unauthorized file system writes, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2023-5834/"}