dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-23173

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 provides direct web-based access to uCPE virtual machines through the Director GUI. By default, the websockify service is exposed on port 6080 and accessible from the internet. This exposure introduces significant risk, as websockify has known weaknesses that can be exploited, potentially leading to remote code execution. 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: Restrict access to TCP port 6080 if uCPE console access is not necessary. 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

The Versa Director SD-WAN platform exposes a websockify service on TCP port 6080 by default, providing direct web-based console access to uCPE virtual machines. This service is internet-accessible and contains known weaknesses that can be exploited for remote code execution.

MitigationImmediately restrict inbound access to TCP port 6080 via firewall rules or ACLs. Plan and execute an upgrade to the remediated software versions when available.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

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
    Run 'rpm -qa | grep -i versa' or 'dpkg -l | grep -i versa' to list installed Versa packages. Check for processes related to Versa Director using 'ps aux | grep -i versa' or 'systemctl list-units | grep versa'.
    Affected if Versa Director software is installed on the system.
  2. Verify websockify service on port 6080
    Run 'netstat -tlnp | grep 6080' or 'ss -tlnp | grep 6080' to check if port 6080 is listening. Also verify with 'lsof -i :6080' or 'nmap -p 6080 localhost'.
    Affected if Port 6080 is open and listening for connections.
  3. Check service binding address
    Run 'ss -tlnp | grep 6080' or 'netstat -tlnp | grep 6080' to see the binding address. Look for 0.0.0.0:6080 or :::6080 which indicates all interfaces, versus 127.0.0.1:6080 for localhost-only.
    Affected if The service binds to 0.0.0.0 or ::: (all interfaces), making it network-accessible.
  4. Test external accessibility of port 6080
    From an external host, run 'nmap -p 6080 <target-ip>' or 'telnet <target-ip> 6080' to confirm the port is reachable from outside the local machine. Check firewall rules with 'iptables -L -n' or 'firewall-cmd --list-all'.
    Affected if Port 6080 is reachable from external network locations or not blocked by firewall.
  5. Confirm websockify console access is enabled
    Inspect Versa Director configuration files in /opt/versa or /etc/versa directories for websockify settings. Check if the web-based console feature for uCPE VMs is configured and enabled.
    Affected if The websockify service is actively providing web console access to virtual machines.

A system is affected if Versa Director is installed with the websockify service listening on port 6080 and that port is accessible from network locations beyond localhost.

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

Immediately restrict inbound access to TCP port 6080 via firewall rules or ACLs. Plan and execute an upgrade to the remediated software versions when available.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-23173 — 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-23173 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