FKIE_CVE-2024-45229

Vulnerability from fkie_nvd - Published: 2024-09-20 19:15 - Updated: 2026-08-25 14:28
Summary
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.

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Director",
          "vendor": "Versa",
          "versions": [
            {
              "lessThan": "22.1.4 20240909",
              "status": "affected",
              "version": "22.1.4 20240909",
              "versionType": "custom"
            },
            {
              "lessThan": "22.1.3 20240909",
              "status": "affected",
              "version": "22.1.3 20240909",
              "versionType": "custom"
            },
            {
              "lessThan": "22.1.2 20240909",
              "status": "affected",
              "version": "22.1.2 20240909",
              "versionType": "custom"
            },
            {
              "lessThan": "22.1.1 20240909",
              "status": "affected",
              "version": "22.1.1 20240909",
              "versionType": "custom"
            },
            {
              "lessThan": "21.2.3 20240909",
              "status": "affected",
              "version": "21.2.3 20240909",
              "versionType": "custom"
            },
            {
              "lessThan": "21.2.2 20240909",
              "status": "affected",
              "version": "21.2.2 20240909",
              "versionType": "custom"
            }
          ]
        }
      ],
      "source": "support@hackerone.com"
    },
    {
      "affectedData": [
        {
          "cpes": [
            "cpe:2.3:a:versa:director:*:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unknown",
          "product": "director",
          "vendor": "versa",
          "versions": [
            {
              "status": "affected",
              "version": "22.1.4"
            },
            {
              "status": "affected",
              "version": "22.1.3"
            },
            {
              "status": "affected",
              "version": "22.1.2"
            },
            {
              "status": "affected",
              "version": "22.1.1"
            },
            {
              "status": "affected",
              "version": "21.2.3"
            },
            {
              "status": "affected",
              "version": "21.2.2"
            }
          ]
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:versa-networks:versa_director:21.2.2:*:*:*:*:*:*:*",
              "matchCriteriaId": "59E2F7B6-200B-4008-A5C6-FD33B05DFF8F",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:versa-networks:versa_director:21.2.3:-:*:*:*:*:*:*",
              "matchCriteriaId": "BB85151A-2B0A-4C44-A63A-B521A1578A4B",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:versa-networks:versa_director:22.1.1:*:*:*:*:*:*:*",
              "matchCriteriaId": "BE334340-8D19-4A10-AB58-B9028D96851C",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:versa-networks:versa_director:22.1.2:-:*:*:*:*:*:*",
              "matchCriteriaId": "2EB7153D-77F2-47E1-BEE0-F2071DF8C21A",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:versa-networks:versa_director:22.1.3:-:*:*:*:*:*:*",
              "matchCriteriaId": "C0CB9A88-8347-45E9-8E80-F46FE1391B8C",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:versa-networks:versa_director:22.1.4:-:*:*:*:*:*:*",
              "matchCriteriaId": "272A25D5-8B29-4919-9C8A-D36DE8B592BF",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "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. \r\n\r\nCurrently, 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 \u0026 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."
    },
    {
      "lang": "es",
      "value": "Versa Director ofrece API REST para orquestaci\u00f3n y administraci\u00f3n. Por dise\u00f1o, ciertas API, como la pantalla de inicio de sesi\u00f3n, la visualizaci\u00f3n de banners y el registro de dispositivos, no requieren autenticaci\u00f3n. Sin embargo, se descubri\u00f3 que para los Directors conectados directamente a Internet, una de estas API se puede explotar inyectando argumentos no v\u00e1lidos en una solicitud GET, lo que potencialmente expone los tokens de autenticaci\u00f3n de otros usuarios que hayan iniciado sesi\u00f3n en ese momento. Estos tokens se pueden usar para invocar API adicionales en el puerto 9183. Este exploit no revela ninguna informaci\u00f3n de nombre de usuario o contrase\u00f1a. Actualmente, no hay workarounds en Versa Director. Sin embargo, si hay un firewall de aplicaciones web (WAF) o una puerta de enlace de API frente a Versa Director, se puede usar para bloquear el acceso a las URL de API vulnerables. /vnms/devicereg/device/* (en los puertos 9182 y 9183) y /versa/vnms/devicereg/device/* (en el puerto 443). Versa recomienda que los Directors se actualicen a una de las versiones de software corregidas. Esta vulnerabilidad no se puede explotar en los Directors de Versa que no est\u00e9n expuestos a Internet. Hemos comprobado que ninguna de las cabeceras alojadas en Versa se ha visto afectada por esta vulnerabilidad. P\u00f3ngase en contacto con el equipo de asistencia t\u00e9cnica de Versa o con el equipo de cuentas de Versa para obtener m\u00e1s ayuda."
    }
  ],
  "id": "CVE-2024-45229",
  "lastModified": "2026-08-25T14:28:04.280",
  "metrics": {
    "cvssMetricV30": [
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "HIGH",
          "baseScore": 6.6,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "HIGH",
          "integrityImpact": "HIGH",
          "privilegesRequired": "HIGH",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H",
          "version": "3.0"
        },
        "exploitabilityScore": 0.7,
        "impactScore": 5.9,
        "source": "support@hackerone.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2024-45229",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2024-09-20T18:45:34.826535Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2024-09-20T19:15:16.080",
  "references": [
    {
      "source": "support@hackerone.com",
      "tags": [
        "Vendor Advisory"
      ],
      "url": "https://security-portal.versa-networks.com/emailbulletins/66e4a8ebda545d61ec2b1ab9"
    }
  ],
  "sourceIdentifier": "support@hackerone.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-306"
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.