dbcve.org
Nexus DashboardApplication · Cisco

CVE-2025-20347

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-27
Fix available
A fix is available. Upgrade to 4.1 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability in the REST API endpoints of Cisco Nexus Dashboard and Cisco Nexus Dashboard Fabric Controller (NDFC) could allow an authenticated, low-privileged, remote attacker to view sensitive information or upload and modify files on an affected device. This vulnerability exists because of missing authorization controls on some REST API endpoints. An attacker could exploit th vulnerability by sending crafted API requests to an affected endpoint. A successful exploit could allow the attacker to perform limited Administrator functions, such as accessing sensitive information regarding HTTP Proxy and NTP configurations, uploading images, and damaging image files on an affected device.

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 confidence

This is a broken access control vulnerability in Cisco Nexus Dashboard and NDFC REST APIs where missing authorization checks on certain endpoints allow low-privileged authenticated users to perform administrative functions. Attackers can access sensitive configuration data (HTTP Proxy, NTP settings) and perform unauthorized file operations including uploads and image file modification.

MitigationApply Cisco's patch when released; until then, restrict API endpoint access via network segmentation and monitor for anomalous API requests from non-administrator accounts.

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
Affected:< 4.1\(1g\)

CVSS 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nexus Dashboard version
    Access the Nexus Dashboard admin interface or use the 'show version' CLI command via SSH to retrieve the installed software version. Compare against the affected range: versions prior to 4.1(1g).
    Affected if Installed version is below 4.1(1g)
  2. Confirm NDFC REST API is enabled
    Check the Nexus Dashboard Fabric Controller (NDFC) configuration settings or API service status to determine if REST API endpoints are exposed and operational.
    Affected if NDFC REST API is enabled and accessible
  3. Review user account privilege levels
    Enumerate user accounts in the Nexus Dashboard user database. Identify accounts with API access that hold roles below Administrator level.
    Affected if Low-privileged users (non-administrator roles) have API authentication credentials
  4. Inspect API access logs for privilege escalation
    Examine API request logs for any instances where non-administrator accounts accessed administrative endpoints, particularly those related to HTTP Proxy configuration, NTP settings, file uploads, or image file modifications.
    Affected if Logs show low-privileged users accessing administrative API endpoints
  5. Verify sensitive config exposure
    Using a low-privileged API account, attempt to query endpoints that expose HTTP Proxy settings, NTP configuration, or file operation interfaces. If these return data without authorization failure, the vulnerability is present.
    Affected if Low-privileged API accounts can retrieve HTTP Proxy, NTP settings, or access file operation endpoints

Environment is affected if Nexus Dashboard version is below 4.1(1g), the REST API is enabled, and low-privileged authenticated users can access administrative endpoints or sensitive configuration data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.1 or later
Fixed in 4.1
Interim mitigation

Apply Cisco's patch when released; until then, restrict API endpoint access via network segmentation and monitor for anomalous API requests from non-administrator accounts.

Recommended fix Moderate confidence

Nexus Dashboard 4.1(1g) or later (NDFC releases aligned with this version)

  1. Verify current Nexus Dashboard version via web UI or API (GET /api/v1/system)
  2. Review upgrade prerequisites and compatibility matrix in Cisco Nexus Dashboard documentation
  3. Schedule a maintenance window as upgrades require downtime
  4. Back up current Nexus Dashboard configuration and any critical data
  5. Download Nexus Dashboard 4.1(1g) or later from Cisco Software Downloads (requires valid Cisco service contract)
  6. Upload the upgrade image via Nexus Dashboard web UI (System > Upgrade) or API
  7. Follow Cisco upgrade procedure to apply the new image
  8. After upgrade, verify the system is healthy and all services are operational
Caveat Standard Cisco upgrade considerations apply - ensure compatibility with connected fabric controllers and review release notes for any behavioral changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nexus Dashboard Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20347 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20347 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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