CVE-2024-2240
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 · uneditedDocker daemon in Brocade SANnav before SANnav 2.3.1b runs without auditing. The vulnerability could allow a remote authenticated attacker to execute various attacks.
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 confidenceThe Docker daemon in Brocade SANnav prior to version 2.3.1b runs without audit logging enabled, meaning all Docker commands and activities executed on the system leave no forensic trail. A remote authenticated attacker with valid SANnav credentials could execute Docker commands to perform various attacks (including container escape, privilege escalation, or deployment of malicious containers) without being detected or traced.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2.3.1bCVSS 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
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SANnav versionLocate the SANnav installation and determine the installed version number. This is typically visible in the SANnav web interface login page, about section, or in the installation documentation.Affected if The installed version is lower than 2.3.1b (for example, 2.3.0, 2.2.x, etc.)
-
Check Docker audit log configurationExamine the Docker daemon configuration file (typically /etc/docker/daemon.json) or the audit rules configuration (usually in /etc/audit/rules.d/ or via auditctl) to determine if Docker command logging is enabled.Affected if No audit rules are configured for Docker, or the Docker daemon.json does not include logging settings that capture command executions.
-
Verify audit service statusConfirm whether the Linux audit daemon (auditd) is running and actively logging events on the system where Docker is installed.Affected if The audit service is not running, or no audit logs are being generated for the Docker daemon and its command-line operations.
A system is affected if it runs a Brocade SANnav version lower than 2.3.1b AND Docker daemon audit logging is not configured or enabled, leaving Docker command executions unlogged.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped2.3.1b
Enable Docker daemon auditing in SANnav and update to SANnav version 2.3.1b or later to remediate this vulnerability. Configure Docker audit rules to log all command executions and API calls.
SANnav 2.3.1b
- Obtain SANnav version 2.3.1b or later from Broadcom support portal at support.broadcom.com
- Review SANnav upgrade documentation for pre-upgrade requirements
- Backup current SANnav configuration and database
- Stop SANnav services before upgrade
- Install SANnav 2.3.1b upgrade package
- Verify Docker daemon auditing is enabled post-upgrade
- Restart SANnav services and validate functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2240 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2240 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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