dbcve.org
Versa DirectorApplication · Versa Networks

CVE-2025-23168

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 implements Two-Factor Authentication (2FA) using One-Time Passcodes (OTP) delivered via email or SMS. Versa Director accepts untrusted user input when dispatching 2FA codes, allowing an attacker who knows a valid username and password to redirect the OTP delivery (SMS/email) to their own device. OTP/TOTP codes are not invalidated after use, enabling reuse by an attacker who has previously intercepted or obtained a valid code. In addition, the 2FA system does not adequately restrict the number or frequency of login attempts. The OTP values are generated from a relatively small keyspace, making brute-force attacks more feasible. 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: 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

Versa Director SD-WAN platform's 2FA implementation contains multiple flaws: it accepts untrusted user input when dispatching OTP codes allowing redirection to attacker-controlled devices, OTP codes remain valid after use enabling reuse, lacks rate limiting on login attempts, and uses a small keyspace vulnerable to brute-force attacks.

MitigationUpgrade Versa Director to the remediated software versions recommended by Versa Networks to address all identified 2FA vulnerabilities.

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 data
Versa DirectorApplication
Affected:= 21.2.2= 21.2.3= 22.1.2= 22.1.3= 22.1.4

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

CVSS:3.1/AV:N/AC:L/PR:L/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 if Versa Director is deployed
    Check for Versa Director services or processes running on the system, or verify its presence in the network inventory
    Affected if Versa Director is installed and running in the environment
  2. Check installed Versa Director version
    Access the Versa Director administrative interface or use the vendor-provided command to retrieve the software version
    Affected if The installed version matches 21.2.2, 21.2.3, 22.1.2, 22.1.3, or 22.1.4
  3. Verify if 2FA/OTP is enabled
    Check the user authentication settings or user account configurations in Versa Director to determine if One-Time Password (OTP) or Two-Factor Authentication is active
    Affected if 2FA/OTP authentication is enabled for any user accounts in the system
  4. Check for OTP-related configuration
    Inspect the OTP or 2FA configuration settings within the Versa Director administrative console or configuration files
    Affected if OTP configuration exists and the system uses a small keyspace or allows OTP code reuse

The environment is affected if Versa Director is running version 21.2.2, 21.2.3, 22.1.2, 22.1.3, or 22.1.4 and 2FA/OTP authentication is enabled for user accounts.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Versa Director to the remediated software versions recommended by Versa Networks to address all identified 2FA vulnerabilities.

Recommended fix Moderate confidence

Contact Versa Networks support to obtain the specific remediated version (advisory states upgrade to 'one of the remediated software versions' but does not specify exact version numbers)

  1. 1. Obtain the specific fixed software version from Versa Networks support portal (security-portal.versa-networks.com or support.versa-networks.com) as the exact remediated version is not specified in the advisory
  2. 2. Back up the current Versa Director configuration and database
  3. 3. Schedule a maintenance window for the upgrade
  4. 4. Download the remediated Versa Director software version from Versa Networks support portal
  5. 5. Follow Versa Networks upgrade procedures to install the new software version
  6. 6. Verify that the 2FA/OTP functionality is working correctly after upgrade
  7. 7. Confirm that the OTP delivery mechanism now properly validates and restricts user input
Caveat Review release notes for any configuration or feature changes between affected and remediated versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Versa Director Scoped from the published advisory
  • Consultation8.0 h
  • Implementation40.0 h
  • Testing16.0 h
  • Review / QA8.0 h
72.0 hours of engineering $12,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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