CVE-2022-25962
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAll versions of the package vagrant.js are vulnerable to Command Injection via the boxAdd function due to improper input sanitization.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe vagrant.js package contains a command injection vulnerability in the boxAdd function due to improper input sanitization. User-supplied input is passed directly to system commands without sanitization, allowing remote attackers to execute arbitrary commands on the host system with the privileges of the Node.js process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if vagrant.js package is installedRun 'npm list vagrant.js' or check package.json for 'vagrant.js' in dependenciesAffected if The package is present in node_modules or listed as a dependency
-
Locate boxAdd function usage in codebaseSearch source files for 'boxAdd' function calls using grep or IDE searchAffected if The boxAdd function is called in the codebase
-
Inspect how boxAdd receives inputExamine the code where boxAdd is called to trace the source of input parameters (look for user-controlled data paths)Affected if User-supplied data (request parameters, CLI arguments, environment variables, or external APIs) flows directly to boxAdd without validation
-
Verify input sanitization is absentReview the boxAdd implementation and its call sites for absence of input validation, escaping, or sanitization functions before command executionAffected if No input validation, escaping, or sanitization is performed on data passed to boxAdd before it reaches system commands
-
Confirm command execution contextCheck if the Node.js process runs with elevated privileges or in a sensitive environment where command injection would be criticalAffected if The application runs with elevated privileges or in a security-sensitive context
You are affected if the vagrant.js package is installed and user-controlled input can reach the boxAdd function without sanitization before command execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version of vagrant.js that implements proper input sanitization and validation in the boxAdd function. If no patch is available, implement input validation and escaping before passing any user input to system commands.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-25962 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data