CVE-2024-2240
CVE-2024-2240 is a high-severity vulnerability in Broadcom Brocade Sannav with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-250.
Key facts
- Severity: High (CVSS 3.x base score 7.2)
- CVSS v4: 8.6
- EPSS exploit prediction: 0% (37th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2024-27196
- Weakness: CWE-250
- Affected product: Broadcom Brocade Sannav
- Published:
- Last modified:
Description
Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. The vulnerability could allow a remote authenticated attacker to execute various attacks.
Frequently asked questions
- What is CVE-2024-2240?
- Docker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. The vulnerability could allow a remote authenticated attacker to execute various attacks.
- How severe is CVE-2024-2240?
- CVE-2024-2240 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2024-2240 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (37th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2024-2240?
- CVE-2024-2240 affects Broadcom Brocade Sannav. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2024-2240?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- Does CVE-2024-2240 have an EU (EUVD) identifier?
- Yes. CVE-2024-2240 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-27196.
- When was CVE-2024-2240 published?
- CVE-2024-2240 was published on 2025-02-14 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:broadcom:brocade_sannav:*:*:*:*:*:*:*:*
More vulnerabilities in Broadcom Brocade Sannav
- CVE-2024-4282 — Critical (CVSS 9.8): Brocade SANnav OVA before SANnav 2.3.1b enables SHA1 deprecated setting for SSH for port 22.
- CVE-2022-23305 — Critical (CVSS 9.8): By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be…
- CVE-2019-16211 — Critical (CVSS 9.8): Brocade SANnav versions before v2.1.0, contain a Plaintext Password Storage vulnerability.
- CVE-2024-3596 — Critical (CVSS 9.0): RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response…
- CVE-2022-23302 — High (CVSS 8.8): JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write…
- CVE-2019-16212 — High (CVSS 8.8): A vulnerability in Brocade SANnav versions before v2.1.0 could allow a remote authenticated attacker to conduct an LDAP…
All CVEs affecting Broadcom Brocade Sannav →
Other CWE-250 vulnerabilities
- CVE-2026-4606 — Critical (CVSS 10.0): GV Edge Recording Manager (ERM) v2.3.1 improperly runs application components with SYSTEM-level privileges, allowing…
- CVE-2022-2634 — Critical (CVSS 10.0): An attacker may be able to execute malicious actions due to the lack of device access protections and device…
- CVE-2026-48584 — Critical (CVSS 9.9): Execution with unnecessary privileges in Azure Synapse allows an authorized attacker to elevate privileges over a…
- CVE-2026-50566 — Critical (CVSS 9.9): Fission is an open-source, Kubernetes-native serverless framework that simplifies the deployment of functions and…
- CVE-2026-44477 — Critical (CVSS 9.9): CloudNativePG is a platform designed to manage PostgreSQL databases within Kubernetes environments. Prior to 1.29.1 and…
- CVE-2026-25212 — Critical (CVSS 9.9): An issue was discovered in Percona PMM before 3.7. Because an internal database user retains specific superuser…