Nexus Dashboard Fabric ControllerApplication · Cisco
CVE-2024-20449
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 · uneditedA vulnerability in Cisco Nexus Dashboard Fabric Controller (NDFC) could allow an authenticated, remote attacker with low privileges to execute arbitrary code on an affected device. This vulnerability is due to improper path validation. An attacker could exploit this vulnerability by using the Secure Copy Protocol (SCP) to upload malicious code to an affected device using path traversal techniques. A successful exploit could allow the attacker to execute arbitrary code in a specific container with the privileges of root.
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 confidenceA path traversal vulnerability in Cisco Nexus Dashboard Fabric Controller allows authenticated low-privilege users to manipulate file paths during SCP uploads, enabling arbitrary code execution within a specific container running as root.
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
Nexus Dashboard Fabric ControllerApplication
>= 12.0.0, <= 12.2.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed version of Cisco Nexus Dashboard Fabric ControllerAccess the Nexus Dashboard web interface and navigate to the About or System Settings section to view the software version, or use the CLI command 'show version' if available via SSH to the fabric controllerAffected if The installed version falls within the range >= 12.0.0 and <= 12.2.2
-
Determine if SCP upload functionality is enabledIn the Nexus Dashboard Fabric Controller web UI, locate the SCP or file transfer settings under Administration > File Management or similar sections, or check the configuration for 'scp-server' or 'scp-enable' settings via CLIAffected if SCP upload access is enabled and accessible to authenticated users, particularly low-privilege accounts
-
Review user account privileges for low-privilege authenticated usersNavigate to Administration > Users/Users and Roles in the web interface, or use the CLI command 'show user-account' to list all configured users and their assigned rolesAffected if Any authenticated user exists with network-operator, network-admin, or similar roles that permit SCP file operations
-
Inspect for unexpected files in the container filesystemIf you have CLI access, use 'ls -la' on the root directory or common upload destinations (such as /var/log, /home, or /tmp) within the fabric controller container to look for suspicious files with unusual timestamps or ownershipAffected if Files exist outside the expected upload directories or show signs of manipulation via path traversal sequences (such as ../../)
You are affected if your Cisco Nexus Dashboard Fabric Controller version is between 12.0.0 and 12.2.2 inclusive AND SCP upload functionality is enabled for authenticated users.
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.
From vendor dataApply Cisco's patch for CVE-2024-20449; until then, restrict or disable SCP access and monitor for unauthorized file uploads.
Fix this in Nexus Dashboard Fabric Controller
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20449 — 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-20449 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