Improper Access ControlWeakness · CWE-284

CVE-2024-45208

CRITICAL · 9.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 →
100/100
Remediation priority · Urgent
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 which makes use of Cisco NCS application service. Active and Standby Directors communicate over TCP ports 4566 and 4570 to exchange High Availability (HA) information using a shared password. Affected versions of Versa Director bound to these ports on all interfaces. An attacker that can access the Versa Director could access the NCS service on port 4566 and exploit it to perform unauthorized administrative actions and perform remote code execution. Customers are recommended to follow the hardening guide. 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.

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's embedded Cisco NCS application service binds to TCP ports 4566 and 4570 on all network interfaces rather than仅限于内部HA通信接口。攻击者只要能访问这些暴露的端口,即可利用共享密码进行未授权管理操作并实现远程代码执行。

Mitigation根据Versa硬化指南限制端口4566和4570的访问,仅允许内部HA接口通信;如可能,将NCS服务绑定改为仅监听内部接口。

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
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 checks

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

  1. Verify Versa Director is installed
    Check if Versa Director software is present on the system by reviewing installed packages or the application directory structure (typically under /opt/versa or similar vendor directories)
    Affected if Versa Director software is found on the system
  2. Identify if NCS service is enabled
    Review the Versa Director configuration or running processes to determine if the embedded Cisco NCS application service is enabled and running
    Affected if The NCS service is running or enabled on the system
  3. Check if port 4566 is listening
    Run 'netstat -tlnp' or 'ss -tlnp' to verify if TCP port 4566 is bound and listening. Use 'ss -tlnp | grep 4566' or check the listening address (0.0.0.0 vs. internal interface IP)
    Affected if Port 4566 is bound to 0.0.0.0 or a non-internal IP address, indicating it is exposed beyond HA interfaces
  4. Check if port 4570 is listening
    Run 'netstat -tlnp' or 'ss -tlnp' to verify if TCP port 4570 is bound and listening. Use 'ss -tlnp | grep 4570' or check the listening address (0.0.0.0 vs. internal interface IP)
    Affected if Port 4570 is bound to 0.0.0.0 or a non-internal IP address, indicating it is exposed beyond HA interfaces
  5. Verify network accessibility of these ports
    Confirm whether ports 4566 and 4570 are reachable from network segments other than the designated internal HA interface by reviewing firewall rules, ACLs, or by attempting a connection test from an external host
    Affected if Ports 4566 and 4570 are accessible from non-HA network segments

If the NCS service is running and ports 4566 or 4570 are bound to all interfaces (0.0.0.0) or accessible from non-internal networks, the system is affected by this vulnerability.

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

根据Versa硬化指南限制端口4566和4570的访问,仅允许内部HA接口通信;如可能,将NCS服务绑定改为仅监听内部接口。

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45208 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45208 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