CVE-2024-20348
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 the Out-of-Band (OOB) Plug and Play (PnP) feature of Cisco Nexus Dashboard Fabric Controller (NDFC) could allow an unauthenticated, remote attacker to read arbitrary files. This vulnerability is due to an unauthenticated provisioning web server. An attacker could exploit this vulnerability through direct web requests to the provisioning server. A successful exploit could allow the attacker to read sensitive files in the PnP container that could facilitate further attacks on the PnP infrastructure.
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 vulnerability exists in the Out-of-Band Plug and Play (PnP) feature of Cisco Nexus Dashboard Fabric Controller. An unauthenticated provisioning web server allows remote attackers to read arbitrary files on the PnP container through direct web requests, potentially exposing sensitive data that could enable further attacks on the PnP infrastructure.
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= 12.1.3= 12.1.3bCVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 installed product and versionAccess the Cisco Nexus Dashboard Fabric Controller admin interface or CLI and retrieve the exact software version number (typically via 'show version' or system information page)Affected if Version is exactly 12.1.3 or 12.1.3b
-
Verify Out-of-Band PnP feature is enabledReview the PnP configuration in the Nexus Dashboard Fabric Controller admin panel or via CLI commands such as 'show pnp status' or 'show running-config pnp'Affected if The Out-of-Band Plug and Play provisioning feature is configured and enabled
-
Confirm unauthenticated provisioning web server statusExamine the PnP service configuration for settings that allow anonymous or unauthenticated access (look for parameters like 'anonymous-access enable', 'guest-enable', or similar in the PnP web server settings)Affected if The unauthenticated provisioning web server is enabled in the PnP configuration
-
Assess network accessibility of PnP serviceReview network access controls, firewall rules, or service listening addresses to determine if the PnP web server port is exposed to untrusted networks or directly reachable from external IP addressesAffected if The PnP web server is network-accessible from untrusted or external networks
The environment is affected only if running version 12.1.3 or 12.1.3b with the PnP feature enabled and the unauthenticated provisioning web server exposed to the network.
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 · scopedOrganizations should disable or restrict the unauthenticated PnP provisioning web server, implement proper authentication on the PnP service, and network-segment the PnP infrastructure to limit exposure to untrusted networks.
NDFC version 12.1.4 or later (contact Cisco TAC for exact fixed release)
- 1. Identify the current Cisco Nexus Dashboard Fabric Controller version by accessing the NDFC web UI or running 'show version' command
- 2. Download the fixed release from Cisco.com software downloads or contact Cisco TAC for the latest patched version
- 3. Review the Cisco Nexus Dashboard Fabric Controller release notes for version 12.1.4 or later for security fixes
- 4. Follow Cisco's standard NDFC upgrade procedure: create a backup, validate compatibility, and schedule maintenance window
- 5. Apply the upgrade to all NDFC cluster nodes according to Cisco upgrade documentation
- 6. After upgrade, verify the NDFC services are operational and confirm the PnP provisioning server is now properly authenticated
- 7. Validate that the vulnerability is remediated by reviewing the system configuration and running any post-upgrade security checks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20348 — 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-20348 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