Digital Network Architecture CenterApplication · Cisco
CVE-2020-3391
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 Cisco Digital Network Architecture (DNA) Center could allow an authenticated, remote attacker to view sensitive information in clear text. The vulnerability is due to insecure storage of certain unencrypted credentials on an affected device. An attacker could exploit this vulnerability by viewing the network device configuration and obtaining credentials that they may not normally have access to. A successful exploit could allow the attacker to use those credentials to discover and manage network devices.
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 confidenceCisco DNA Center stores certain credentials in an insecure, unencrypted manner within the network device configuration. An authenticated attacker with access to view device configurations can retrieve these cleartext credentials, potentially gaining elevated access to discover and manage network devices they should not have permissions for.
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
Digital Network Architecture CenterApplication
< 1.2.10CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine installed Cisco DNA Center versionAccess the Cisco DNA Center admin UI or use the CLI command 'show version' or check the system about page in the application. Alternatively, query the API endpoint for system information.Affected if The installed version is lower than 1.2.10 (for example, 1.1.x, 1.2.0-1.2.9)
-
Verify if device onboarding is configuredCheck whether Cisco DNA Center has been used to discover, template, or manage network devices. Review the device provisioning or design sections in the UI.Affected if Network devices have been added, provisioned, or managed through Cisco DNA Center
-
Inspect stored device configurations for credentialsExport or view a device configuration template or saved configuration from Cisco DNA Center. Look for lines containing username, password, secret, or key entries in cleartext format.Affected if Device configurations or templates contain unencrypted or cleartext credentials
-
Review user access to device configurationsCheck the user roles and permissions in Cisco DNA Center under Administration > Users and Roles. Identify which users or roles have permission to view exported device configurations or use configuration templates.Affected if Users beyond the administrator account have access to view or export device configurations
You are affected if your Cisco DNA Center version is below 1.2.10 and you have used it to manage network devices, as credentials may be stored in cleartext within accessible device configurations.
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.
From vendor data1.2.10
Apply the Cisco patch for CVE-2020-3391 when available, and rotate all credentials that may have been exposed. Review access controls to ensure only authorized personnel can view device configurations.
Fix this in Digital Network Architecture Center
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3391 — 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-2020-3391 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