Digital Network Architecture CenterApplication · Cisco
CVE-2018-0222
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 unauthenticated, remote attacker to log in to an affected system by using an administrative account that has default, static user credentials. The vulnerability is due to the presence of undocumented, static user credentials for the default administrative account for the affected software. An attacker could exploit this vulnerability by using the account to log in to an affected system. A successful exploit could allow the attacker to log in to the affected system and execute arbitrary commands with root privileges. This vulnerability affects all releases of Cisco DNA Center Software prior to Release 1.1.3. Cisco Bug IDs: CSCvh98929.
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 confidenceA critical default credential vulnerability in Cisco DNA Center allows unauthenticated remote attackers to gain root access by leveraging undocumented static credentials for the default administrative account. Attackers can execute arbitrary commands with full root privileges on affected systems running any version prior to Release 1.1.3.
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.1.3CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 if Cisco DNA Center is deployedReview your network infrastructure to determine if Cisco DNA Center (formerly Cisco DNA) is installed. Check for associated appliances, VMs, or management interfaces on your network.Affected if Cisco DNA Center is present in your environment
-
Determine the installed versionAccess the Cisco DNA Center administrative interface or check the system documentation/package metadata to identify the currently installed release version.Affected if The version is less than 1.1.3
-
Verify the default admin account statusCheck whether the default administrative account (typically 'admin') remains configured and accessible on the system.Affected if The default admin account exists and is accessible using the undocumented static credentials
Your environment is affected if Cisco DNA Center is running any version prior to Release 1.1.3 and the default administrative account with undocumented static credentials is present and accessible.
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 · scoped1.1.3
Upgrade to Cisco DNA Center Release 1.1.3 or later to remove the undocumented default credentials. Alternatively, implement network segmentation and access controls to limit exposure to the management interface.
Cisco DNA Center Release 1.1.3 or later
- Identify current Cisco DNA Center version by accessing the GUI or using CLI command 'show version'
- Schedule a maintenance window for the upgrade
- Backup current Cisco DNA Center configuration and data
- Download Cisco DNA Center Software Release 1.1.3 or later from Cisco.com
- Upgrade Cisco DNA Center to Release 1.1.3 or later following Cisco's official upgrade guide
- Verify the upgrade was successful by checking the version
- Confirm the undocumented static credentials are no longer present
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Digital Network Architecture Center
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0222 — 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-2018-0222 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