dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-23170

MEDIUM · 6.7 CVSS v3.1 Published 2025-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
The Versa Director SD-WAN orchestration platform includes functionality to initiate SSH sessions to remote CPEs and the Director shell via Shell-In-A-Box. The underlying Python script, shell-connect.py, is vulnerable to command injection through the user argument. This allows an attacker to execute arbitrary commands on the system. Exploitation Status: Versa Networks is not aware of any reported instance where this vulnerability was exploited. Proof of concept for this vulnerability has been disclosed by third party security researchers. Workarounds or Mitigation: There are no workarounds to disable the GUI option. Versa recommends that Director be upgraded to one of the remediated software versions.

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 confidence

Command injection vulnerability in Versa Director's shell-connect.py Python script. The user argument is not properly sanitized when initiating SSH sessions to remote CPEs and the Director shell via Shell-In-A-Box, allowing an attacker to inject and execute arbitrary OS commands.

MitigationUpgrade Versa Director to a remediated software version as recommended by Versa Networks. No workarounds are available to disable the vulnerable GUI functionality.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Versa Director installation
    Check if Versa Director is installed on the system by looking for installation directories such as /opt/versa, /var/versa, or searching for the 'versa' process running on the system
    Affected if Versa Director software is present on the system
  2. Determine Versa Director version
    Run the command 'rpm -q versa-director' or check /opt/versa/director/version file if it exists to obtain the installed version number
    Affected if The installed version is within the affected range and has not been patched
  3. Locate shell-connect.py script
    Search for the shell-connect.py script in common paths such as /opt/versa/director/scripts/ or /opt/versa/director/gui/ using 'find /opt -name shell-connect.py 2>/dev/null'
    Affected if The shell-connect.py script exists and is an older, unpatched version lacking input sanitization for the user argument
  4. Verify GUI Shell-In-A-Box functionality is enabled
    Check if the Versa Director GUI service and Shell-In-A-Box feature are accessible and enabled by attempting to access the Director web interface
    Affected if The GUI and Shell-In-A-Box functionality are exposed and accessible to users or attackers
  5. Review access logs for suspicious shell-connect activity
    Examine Versa Director logs in /var/versa/director/logs/ for entries containing shell-connect.py and unusual command patterns or unexpected arguments
    Affected if Log entries show unexpected parameters, command injection attempts, or unauthorized shell sessions

The environment is affected if Versa Director is running with an unpatched version and the GUI Shell-In-A-Box feature is accessible, allowing potential command injection via the shell-connect.py script.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Versa Director to a remediated software version as recommended by Versa Networks. No workarounds are available to disable the vulnerable GUI functionality.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23170 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-23170 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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