Nexus DashboardApplication · Cisco
CVE-2024-20477
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 a specific REST API endpoint of Cisco NDFC could allow an authenticated, low-privileged, remote attacker to upload or delete files on an affected device. This vulnerability exists because of missing authorization controls on the affected REST API endpoint. An attacker could exploit this vulnerability by sending crafted API requests to the affected endpoint. A successful exploit could allow the attacker to upload files into a specific container or delete files from a specific folder within that container. This vulnerability only affects a specific REST API endpoint and does not affect the web-based management interface.
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 · moderate confidenceThis is an authorization bypass vulnerability in a specific Cisco NDFC (Nexus Dashboard Fabric Controller) REST API endpoint. The endpoint lacks proper authorization controls, allowing authenticated low-privilege users to upload files to or delete files from a specific container within the system.
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 DashboardApplication
< 3.2\(1e\)
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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
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 installed Cisco Nexus Dashboard versionAccess the Nexus Dashboard admin UI or use the API/CLI to retrieve the current software version (typically via 'show version' or the /api/system management endpoint)Affected if Version is below 3.2(1e)
-
Identify installed Cisco NDFC versionAccess the NDFC admin UI or use the API/CLI to retrieve the current software version (typically via 'show version' or the /api/system management endpoint)Affected if Version is >= 12.0.0 and < 12.2.2
-
Confirm the affected REST API endpoint is accessibleVerify network accessibility to the NDFC REST API endpoints (typically port 443/HTTPS). Check if the specific container endpoint is reachable from the network where low-privilege users operateAffected if The REST API endpoint is exposed to low-privilege users without network segmentation
-
Identify low-privilege user access to the APIReview user accounts and roles configured in Nexus Dashboard or NDFC. Determine if any authenticated users with limited/reader-level privileges can access the file upload/delete API functionalityAffected if Low-privilege (non-admin) users are authenticated and can reach the API
-
Audit API access logs for the affected endpointReview API access logs or audit trails for POST/DELETE requests to the specific container endpoint by users with roles below administratorAffected if Logs show file upload or delete operations performed by low-privilege users
You are affected if your Nexus Dashboard version is < 3.2(1e) or your NDFC version is >= 12.0.0 and < 12.2.2, and the REST API endpoint is accessible to authenticated low-privilege 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.
dbcve · scoped3.212.2.2
Apply the vendor patch when available. Until then, restrict access to the affected REST API endpoint to only highly privileged users via network segmentation or API gateway controls.
Nexus Dashboard Fabric Controller: 12.2.2 or later | Nexus Dashboard: 3.2(1e) or later
- 1. Identify the current version of Cisco Nexus Dashboard Fabric Controller (NDFC) or Nexus Dashboard by checking the device management interface or using 'show version' command
- 2. For Nexus Dashboard Fabric Controller: Plan upgrade to version 12.2.2 or later
- 3. For Nexus Dashboard: Plan upgrade to version 3.2(1e) or later
- 4. Schedule a maintenance window as upgrades require downtime
- 5. Backup the current configuration and ensure you have a rollback plan
- 6. Download the appropriate software update from Cisco.com or your Cisco support portal
- 7. Follow Cisco's standard upgrade procedure for your specific deployment (single node, cluster, etc.)
- 8. After upgrade, verify the version is running the fixed release using 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nexus Dashboard
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20477 — 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-20477 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