CVE-2025-34075
Vulnerability Scoring
Analysis In Progress
CVE-2025-34075 Vulnerability Analysis & Exploit Details
CVE-2025-34075
Attack Complexity Details
-
Attack Complexity:
Attack Complexity Analysis In Progress
-
Attack Vector:
Attack Vector Under Analysis
-
Privileges Required:
None
No authentication is required for exploitation.
-
Scope:
Impact is confined to the initially vulnerable component.
-
User Interaction:
None
No user interaction is necessary for exploitation.
CVE-2025-34075 Details
Status: Awaiting Analysis
Last updated: 🕒 03 Jul 2025, 15:13 UTC
Originally published on: 🕗 02 Jul 2025, 20:15 UTC
CVSS Release:
CVE-2025-34075 Vulnerability Summary
CVE-2025-34075: An authenticated virtual machine escape vulnerability exists in HashiCorp Vagrant when using the default synced folder configuration. By design, Vagrant automatically mounts the host system’s project directory into the guest VM under /vagrant (or C:\vagrant on Windows). This includes the Vagrantfile configuration file, which is a Ruby script evaluated by the host every time a vagrant command is executed in the project directory. If a low-privileged attacker obtains shell access to the guest VM, they can append arbitrary Ruby code to the mounted Vagrantfile. When a user on the host later runs any vagrant command, the injected code is executed on the host with that user’s privileges. While this shared-folder behavior is well-documented by Vagrant, the security implications of Vagrantfile execution from guest-writable storage are not explicitly addressed. This effectively enables guest-to-host code execution in multi-tenant or adversarial VM scenarios.
Assessing the Risk of CVE-2025-34075
Access Complexity Graph
The exploitability of CVE-2025-34075 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).
Exploitability Analysis for CVE-2025-34075
No exploitability data is available for CVE-2025-34075.
Understanding AC and PR
A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.
Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.
Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.
CVSS Score Breakdown Chart
Above is the CVSS Sub-score Breakdown for CVE-2025-34075, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.
CIA Impact Analysis
Below is the Impact Analysis for CVE-2025-34075, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.
-
Confidentiality:
None
CVE-2025-34075 does not compromise confidentiality.
-
Integrity:
None
CVE-2025-34075 does not impact data integrity.
-
Availability:
None
CVE-2025-34075 does not affect system availability.
CVE-2025-34075 References
External References
- https://developer.hashicorp.com/vagrant
- https://developer.hashicorp.com/vagrant/docs/synced-folders/basic_usage
- https://developer.hashicorp.com/vagrant/docs/vagrantfile
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/local/vagrant_synced_folder_vagrantfile_breakout.rb
- https://vulncheck.com/advisories/hashicorp-vagrant-synced-folder-vagrantfile-breakout
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/multi/local/vagrant_synced_folder_vagrantfile_breakout.rb
CWE Common Weakness Enumeration
CWE-668Protect Your Infrastructure against CVE-2025-34075: Combat Critical CVE Threats
Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.
Other 5 Recently Published CVEs Vulnerabilities
- CVE-2025-8146 – The Qi Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's TypeOut Text widget in all versions ...
- CVE-2025-7694 – The Woffice Core plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the woffice_file_manager...
- CVE-2025-6078 – Partner Software's Partner Software application and Partner Web application allows an authenticated user to add notes on the 'Notes' page when view...
- CVE-2025-6077 – Partner Software's Partner Software Product and corresponding Partner Web application use the same default username and password for the administra...
- CVE-2025-6076 – Partner Software's Partner Software application and Partner Web application do not sanitize files uploaded on the "reports" tab, allowing an authen...