Vulnerabilities in pkg:golang/github.com/hashicorp/vagrant

PACKAGE
Advisory Identifier: GHSA-47xw-vw6m-w9fq
Share
Advisory Summary

CVE-2023-5834 is a LOW (CVSS 3.8) hashicorp vagrant insecure operation on vulnerability (CWE-59: Improper Link Resolution Before File Access ('Link Following')) affecting Github.com/hashicorp/vagrant libraries in the Go ecosystem. The issue involves hashicorp vagrant insecure operation on windows junction / mount point vulnerability. Remediation is available by upgrading affected packages to version 2.4.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/hashicorp/vagrant

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/hashicorp/vagrant. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-47xw-vw6m-w9fq CVE-2023-5834 LOW HashiCorp Vagrant Insecure Operation on Windows Junction / Mount Point vulnerability

CVE-2023-5834 at a Glance

CVE Identifier CVE-2023-5834
GHSA Identifier GHSA-47xw-vw6m-w9fq
Severity LOW
CVSS v3.1 Base Score 3.8
CWE Classification CWE-59: Improper Link Resolution Before File Access ('Link Following')
Affected Product Github.com/hashicorp/vagrant
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2023-5834

To remediate this vulnerability, upgrade all affected Github.com/hashicorp/vagrant dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/hashicorp/vagrant fixed: 2.4.0 
Upgrade github.com/hashicorp/vagrant to 2.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/hashicorp/vagrant

How to Check if You Are Affected

To determine whether your application is affected by CVE-2023-5834, inspect your project dependencies for Github.com/hashicorp/vagrant:

inspect dependencies for github.com/hashicorp/vagrant

Analyze the terminal output to locate any version of Github.com/hashicorp/vagrant in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.4.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following'), where the product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource. In Github.com/hashicorp/vagrant, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2023-5834 Affected Github.com/hashicorp/vagrant Versions

1 component(s)
Fixed Versions:
2.4.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/hashicorp/vagrant
golang/github.com/hashicorp/vagrant
Go
< 2.4.0
2.4.0

References

NVD — CVE-2023-5834 NVD
https://nvd.nist.gov/vuln/detail/CVE-2023-5834
discuss.hashicorp.com/t/hcsec-2023-31-vag... WEB
https://discuss.hashicorp.com/t/hcsec-2023-31-vagrant-s-windows-installer-allowed-directory-junction-write/59568
Github.com/hashicorp/vagrant Source Repository REPOSITORY
https://github.com/hashicorp/vagrant

Frequently Asked Questions

What is CVE-2023-5834?
CVE-2023-5834 is a security vulnerability in Github.com/hashicorp/vagrant involving HashiCorp Vagrant Insecure Operation on Windows Junction / Mount Point vulnerability under CWE-59: Improper Link Resolution Before File Access ('Link Following').
Which Github.com/hashicorp/vagrant versions are affected?
Affected versions include releases prior to 2.4.0 across affected packages: github.com/hashicorp/vagrant.
What version fixes CVE-2023-5834?
Upgrading to 2.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/hashicorp/vagrant affected?
Yes, github.com/hashicorp/vagrant is affected in releases prior to 2.4.0. Upgrade your dependency to 2.4.0 or later.
What is the CVSS score of CVE-2023-5834?
CVE-2023-5834 has a CVSS v3.1 base score of 3.8 (LOW) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N.
What CWE is associated with CVE-2023-5834?
CVE-2023-5834 is classified under CWE-59: Improper Link Resolution Before File Access ('Link Following') (The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.).
How can I check Go dependencies for CVE-2023-5834?
Run the dependency tree command: 'inspect dependencies for github.com/hashicorp/vagrant'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-47xw-vw6m-w9fq",
  "modified" : "2023-10-31T21:35:21Z",
  "published" : "2023-10-28T00:30:31Z",
  "aliases" : [ "CVE-2023-5834" ],
  "summary" : "HashiCorp Vagrant Insecure Operation on Windows Junction / Mount Point vulnerability",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/hashicorp/vagrant"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "2.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-5834"
  }, {
    "type" : "WEB",
    "url" : "https://discuss.hashicorp.com/t/hcsec-2023-31-vagrant-s-windows-installer-allowed-directory-junction-write/59568"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/hashicorp/vagrant"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-1386", "CWE-59" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-10-31T21:35:21Z",
    "nvd_published_at" : "2023-10-27T22:15:09Z"
  }
}