CVE-2020-3538 is a medium severity (CVSS 4.6) path traversal flaw in a REST API endpoint of Cisco Data Center Network Manager. An authenticated remote attacker could overwrite or list arbitrary files on the device. Cisco's advisory lists releases earlier than 11.4(1) as affected, 11.4(1) or later as fixed, and offers no workarounds.
What's affected
- Cisco Data Center Network Manager (DCNM) software releases earlier than 11.4(1), per Cisco's advisory.
- Fixed: release 11.4(1) and later. Cisco states there are no workarounds.
The record scores it 4.6 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.
How to check if you're exposed
Cisco publishes the exact check in the advisory, so start there. In general, log in to the product and read the running software release from its version page or CLI, then compare it with the fixed release in the advisory. Do not rely on the marketing name of the release alone. For DCNM, the running release is shown in the web interface about page. Anything earlier than 11.4(1) needs an upgrade.
What to do now
- Find every DCNM instance in your data center management network, including lab and disaster recovery copies.
- Read the running release and compare it with 11.4(1).
- Plan an upgrade to 11.4(1) or a later release, following Cisco's upgrade guide for your current version.
- Until the upgrade, limit who holds accounts on the REST API, since the flaw needs a valid login.
- Review the files an API account could reach, and rotate credentials if you suspect misuse.
After you patch, record the new version for Cisco DCNM in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.
Why it matters
The weakness is a path restriction that is not enforced strictly enough. The REST endpoint accepts a file path from the caller and does not keep it inside the intended directory, so a crafted request can reach other files. The record also notes that the attack needs a logged in user and some user interaction, which is why the score is moderate.
A moderate score still matters on a network controller. A device that manages switching fabric holds configuration and credentials, so an overwrite or file listing can be a stepping stone. The record is dated November 2024, although Cisco's fix dates from the 11.4(1) release.
To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.
Quick check
Does this flaw need a login?
Yes. The record describes an authenticated, remote attacker, with low privileges required and user interaction needed. That limits exposure but does not remove it, because any valid account is enough.
How do I find every place Cisco DCNM is used?
Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.
Sources
Last reviewed: 19 October 2026.