FKIE_CVE-2024-20371

Vulnerability from fkie_nvd - Published: 2024-11-06 17:15 - Updated: 2026-06-17 07:06
Severity
5.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Summary
A vulnerability in the access control list (ACL) programming of Cisco Nexus 3550-F Switches could allow an unauthenticated, remote attacker to send traffic that should be blocked to the management interface of an affected device.  This vulnerability exists because ACL deny rules are not properly enforced at the time of device reboot. An attacker could exploit this vulnerability by attempting to send traffic to the management interface of an affected device. A successful exploit could allow the attacker to send traffic to the management interface of the affected device.
References
psirt@cisco.comhttps://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-3550-acl-bypass-mhskZc2q
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unknown",
          "product": "Cisco Nexus 3550 System Software",
          "vendor": "Cisco",
          "versions": [
            {
              "status": "affected",
              "version": "3550-F_1.11.3"
            },
            {
              "status": "affected",
              "version": "3550-F_1.12.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.16.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.17.1"
            },
            {
              "status": "affected",
              "version": "3550-F_1.11.1"
            },
            {
              "status": "affected",
              "version": "3550-F_1.11.2"
            },
            {
              "status": "affected",
              "version": "3550-F_1.15.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.13.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.14.0"
            }
          ]
        }
      ],
      "source": "psirt@cisco.com"
    },
    {
      "affectedData": [
        {
          "cpes": [
            "cpe:2.3:o:cisco:nexus_3550_firmware:*:*:*:*:*:*:*:*"
          ],
          "defaultStatus": "unknown",
          "product": "nexus_3550_firmware",
          "vendor": "cisco",
          "versions": [
            {
              "status": "affected",
              "version": "3550-F_1.11.3"
            },
            {
              "status": "affected",
              "version": "3550-F_1.12.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.16.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.17.1"
            },
            {
              "status": "affected",
              "version": "3550-F_1.11.1"
            },
            {
              "status": "affected",
              "version": "3550-F_1.11.2"
            },
            {
              "status": "affected",
              "version": "3550-F_1.15.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.13.0"
            },
            {
              "status": "affected",
              "version": "3550-F_1.14.0"
            }
          ]
        }
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "A vulnerability in the access control list (ACL) programming of Cisco Nexus 3550-F Switches could allow an unauthenticated, remote attacker to send traffic that should be blocked to the management interface of an affected device.\u0026nbsp;\r\n\r\nThis vulnerability exists because ACL deny rules are not properly enforced at the time of device reboot. An attacker could exploit this vulnerability by attempting to send traffic to the management interface of an affected device. A successful exploit could allow the attacker to send traffic to the management interface of the affected device."
    },
    {
      "lang": "es",
      "value": "Una vulnerabilidad en la programaci\u00f3n de la lista de control de acceso (ACL) de los conmutadores Cisco Nexus 3550-F podr\u00eda permitir que un atacante remoto no autenticado env\u00ede tr\u00e1fico que deber\u00eda estar bloqueado a la interfaz de administraci\u00f3n de un dispositivo afectado. Esta vulnerabilidad existe porque las reglas de denegaci\u00f3n de ACL no se aplican correctamente en el momento del reinicio del dispositivo. Un atacante podr\u00eda aprovechar esta vulnerabilidad al intentar enviar tr\u00e1fico a la interfaz de administraci\u00f3n de un dispositivo afectado. Una explotaci\u00f3n exitosa podr\u00eda permitir al atacante enviar tr\u00e1fico a la interfaz de administraci\u00f3n del dispositivo afectado."
    }
  ],
  "id": "CVE-2024-20371",
  "lastModified": "2026-06-17T07:06:51.253",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 5.3,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "NONE",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 1.4,
        "source": "psirt@cisco.com",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2024-20371",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2024-11-06T17:21:00.515441Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2024-11-06T17:15:14.187",
  "references": [
    {
      "source": "psirt@cisco.com",
      "url": "https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-3550-acl-bypass-mhskZc2q"
    }
  ],
  "sourceIdentifier": "psirt@cisco.com",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-264"
        }
      ],
      "source": "psirt@cisco.com",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

Loading timeline…




    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.