Nexus Dashboard Fabric ControllerApplication · Cisco
CVE-2024-20490
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 logging function of Cisco Nexus Dashboard Fabric Controller (NDFC) and Cisco Nexus Dashboard Orchestrator (NDO) could allow an attacker with access to a tech support file to view sensitive information. This vulnerability exists because HTTP proxy credentials could be recorded in an internal log that is stored in the tech support file. An attacker could exploit this vulnerability by accessing a tech support file that is generated from an affected system. A successful exploit could allow the attacker to view HTTP proxy server admin credentials in clear text that are configured on Nexus Dashboard to reach an external network. Note: Best practice is to store debug logs and tech support files safely and to share them only with trusted parties because they may contain sensitive information.
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 logging function in Cisco Nexus Dashboard Fabric Controller (NDFC) and Nexus Dashboard Orchestrator (NDO) writes HTTP proxy credentials in clear text to internal logs. These logs are included in tech support files generated by the system. An attacker with access to these tech support files can extract and use the proxy admin credentials.
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.1.0, < 12.2.2.241
Nexus Dashboard InsightsApplication
< 6.4.0>= 6.5.0, < 6.5.1.32
Nexus Dashboard OrchestratorApplication
< 4.2\(3o\)>= 4.4.0, < 4.4.1.1012CVSS 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
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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 Cisco Nexus Dashboard productLog into the Nexus Dashboard web UI and navigate to the main dashboard or 'About' page to determine which product component is running (NDFC, NDI, or NDO)Affected if Product is Nexus Dashboard Fabric Controller, Nexus Dashboard Insights, or Nexus Dashboard Orchestrator
-
Check the installed version against affected rangesFrom the Nexus Dashboard UI, view the version information. For NDFC: check if version is >= 12.1.0 and < 12.2.2.241. For NDI: check if version is < 6.4.0, or >= 6.5.0 and < 6.5.1.32. For NDO: check if version is < 4.2(3o) or >= 4.4.0 and < 4.4.1.1012Affected if Installed version falls within any of the affected version ranges listed
-
Determine if an HTTP proxy is configuredNavigate to the Nexus Dashboard admin settings or network configuration to check if an HTTP proxy is configured for external network accessAffected if An HTTP proxy is configured and enabled for the Nexus Dashboard to reach external networks
-
Locate and inspect tech support files for exposed credentialsAccess the tech support or diagnostics export functionality in the Nexus Dashboard UI and download any existing support bundles. Search within the extracted files for plain-text strings matching proxy credentials, looking for patterns like 'proxy', 'password', or credential file contents in log or config filesAffected if Tech support files contain clear-text proxy credentials or username/password combinations for the configured HTTP proxy
A user is affected if they are running any of the three Nexus Dashboard products within the specified version ranges AND have an HTTP proxy configured AND their tech support files contain exposed proxy credentials.
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 · scoped4.24.4.1.10126.4.0
Apply the Cisco vendor patch when released and implement strict access controls on tech support files, sharing only with trusted parties until the patch is applied.
Nexus Dashboard Fabric Controller: 12.2.2.241 or later | Nexus Dashboard Insights: 6.4.0+ or 6.5.1.32+ | Nexus Dashboard Orchestrator: 4.2(3o)+ or 4.4.1.1012+
- 1. Identify the affected Cisco Nexus Dashboard product (NDFC, NDI, or NDO) currently deployed in your environment
- 2. Generate a backup of current configuration before upgrading
- 3. For Nexus Dashboard Fabric Controller: upgrade to version 12.2.2.241 or later
- 4. For Nexus Dashboard Insights: upgrade to version 6.4.0 or later, or 6.5.1.32 or later if using 6.5.x branch
- 5. For Nexus Dashboard Orchestrator: upgrade to version 4.2(3o) or later, or 4.4.1.1012 or later if using 4.4.x branch
- 6. After upgrade, verify the tech support file generation process no longer logs proxy credentials
- 7. If tech support files were previously shared, rotate the HTTP proxy credentials that may have been exposed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nexus Dashboard Fabric Controller
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20490 — 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-20490 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