dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2024-45229

MEDIUM · 6.6 CVSS v3.0 Published 2024-09-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
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 offers REST APIs for orchestration and management. By design, certain APIs, such as the login screen, banner display, and device registration, do not require authentication. However, it was discovered that for Directors directly connected to the Internet, one of these APIs can be exploited by injecting invalid arguments into a GET request, potentially exposing the authentication tokens of other currently logged-in users. These tokens can then be used to invoke additional APIs on port 9183. This exploit does not disclose any username or password information. Currently, there are no workarounds in Versa Director. However, if there is Web Application Firewall (WAF) or API Gateway fronting the Versa Director, it can be used to block access to the URLs of vulnerable API. /vnms/devicereg/device/* (on ports 9182 & 9183) and /versa/vnms/devicereg/device/* (on port 443). Versa recommends that Directors be upgraded to one of the remediated software versions. This vulnerability is not exploitable on Versa Directors not exposed to the Internet.We have validated that no Versa-hosted head ends have been affected by this vulnerability. Please contact Versa Technical Support or Versa account team for any further assistance.

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

An authentication token leakage vulnerability in Versa Director allows unauthenticated attackers on Internet-facing instances to inject malformed arguments into GET requests targeting device registration APIs, potentially exposing active session tokens of legitimate users. These stolen tokens can then be used to authenticate to management APIs on port 9183, achieving unauthorized access without requiring valid credentials.

MitigationUpgrade Versa Director to vendor-remediated versions; for interim protection, deploy a WAF or API Gateway to block access to the vulnerable /vnms/devicereg/device/* and /versa/vnms/devicereg/device/* endpoints.

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

CVSS:3.0/AV:N/AC:H/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 and version
    Run 'versa-director --version' or check /opt/versa director version files; compare against any vendor-provided fixed versions
    Affected if Versa Director is installed and version is not yet patched
  2. Determine if the device registration API endpoints are Internet-accessible
    Attempt a GET request to http://<host>/vnms/devicereg/device/ and http://<host>/versa/vnms/devicereg/device/ from an external network location; check if HTTP response is received
    Affected if These endpoints respond to unauthenticated requests from the internet
  3. Check if management API port 9183 is externally exposed
    Run 'nc -zv <host> 9183' or 'nmap -p 9183 <host>' from an external network; verify the port accepts connections
    Affected if Port 9183 is reachable from untrusted networks
  4. Inspect access logs for anomalous device registration requests
    Review Versa Director logs in /var/log/versa director or equivalent for GET requests to /vnms/devicereg/device/* with malformed arguments or suspicious patterns
    Affected if Logs show malformed or suspicious GET requests to device registration endpoints from unfamiliar sources
  5. Verify if WAF or API Gateway protection is deployed in front of Versa Director
    Review network architecture diagrams or firewall policies to determine if a WAF or API Gateway filters incoming traffic to Versa Director before it reaches the application
    Affected if No WAF or API Gateway protection is in place and the system is Internet-facing

A user is affected if Versa Director is Internet-facing with the device registration endpoints exposed and no protective filtering blocks malformed requests to those endpoints.

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 vendor-remediated versions; for interim protection, deploy a WAF or API Gateway to block access to the vulnerable /vnms/devicereg/device/* and /versa/vnms/devicereg/device/* endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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