CVE-2024-2240: Docker implementation in Brocade SANnav is missing Audit Rules.
First published: Fri Feb 14 2025(Updated: )
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.
Credit: sirt@brocade.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Broadcom SANnav OVA | <2.3.1b |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-2240?
CVE-2024-2240 is classified as a moderate severity vulnerability.
What type of attacks could be executed due to CVE-2024-2240?
CVE-2024-2240 could allow a remote authenticated attacker to execute various unauthorized actions on the Docker daemon.
How do I fix CVE-2024-2240?
To fix CVE-2024-2240, upgrade Brocade SANnav to version 2.3.1b or later.
Who is affected by CVE-2024-2240?
CVE-2024-2240 affects users running Brocade SANnav versions prior to 2.3.1b.
Is there an audit feature impacted in CVE-2024-2240?
Yes, CVE-2024-2240 highlights a lack of auditing in the Docker daemon of Brocade SANnav.
- agent/weakness
- agent/title
- agent/type
- agent/references
- agent/first-publish-date
- agent/description
- collector/nvd-api
- source/NVD
- agent/severity
- agent/source
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/brocade
- canonical/broadcom sannav ova