CVE-2020-3446
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 Virtual Wide Area Application Services (vWAAS) with Cisco Enterprise NFV Infrastructure Software (NFVIS)-bundled images for Cisco ENCS 5400-W Series and CSP 5000-W Series appliances could allow an unauthenticated, remote attacker to log into the NFVIS CLI of an affected device by using accounts that have a default, static password. The vulnerability exists because the affected software has user accounts with default, static passwords. An attacker with access to the NFVIS CLI of an affected device could exploit this vulnerability by logging into the CLI. A successful exploit could allow the attacker to access the NFVIS CLI with administrator privileges.
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 confidenceDefault credential vulnerability in Cisco vWAAS with NFVIS-bundled images for ENCS 5400-W and CSP 5000-W Series appliances. User accounts ship with default, static passwords allowing unauthenticated remote attackers to gain administrator-level access to the NFVIS CLI.
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= 6.4\(1\)= 6.4\(3d\)= 6.4\(1\)= 6.4\(3d\)= 6.4\(1\)= 6.4\(3d\)= 6.4\(1\)= 6.4\(3d\)= 6.4\(1\)= 6.4\(3d\)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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 the appliance model and confirm it is an affected ENCS or CSP seriesLog into the device or check hardware inventory to identify if the model is ENCS 5406 W, ENCS 5408 W, ENCS 5412 W, CSP 5228 W, or CSP 5436 WAffected if The appliance is one of these five specific models
-
Check the NFVIS firmware versionAccess the NFVIS CLI or web interface and run 'show version' or check the firmware version displayed in the system informationAffected if The NFVIS firmware version is 6.4(1) or 6.4(3d)
-
Verify whether default NFVIS administrator credentials are still configuredCheck the NFVIS user accounts by logging into the NFVIS CLI and running 'show user-account' or by reviewing the local authentication configurationAffected if The default administrator account (such as 'admin') has never had its password changed from the factory default
-
Confirm NFVIS CLI is network-accessibleCheck the NFVIS network configuration to determine if the CLI management interface is reachable from remote networks or is bound to an external interfaceAffected if NFVIS CLI management is accessible from network segments outside the trusted internal network
The environment is affected if the appliance is an ENCS 5406/5408/5412 W or CSP 5228/5436 W running NFVIS firmware version 6.4(1) or 6.4(3d) with default credentials still configured and the NFVIS CLI exposed to accessible networks.
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 · scopedImmediately change all default passwords to strong, unique credentials and restrict NFVIS CLI access to prevent unauthorized remote authentication.
Fixed release as specified in Cisco Security Advisory for CVE-2020-3446 (contact Cisco TAC for specific version number)
- Identify the specific Cisco ENCS 5400-W Series or CSP 5000-W Series appliance model running the affected firmware versions 6.4(1) or 6.4(3d)
- Contact Cisco TAC or check the Cisco Security Advisory for CVE-2020-3446 to obtain the fixed release
- Upgrade the NFVIS firmware to the fixed release version indicated in the Cisco advisory
- After upgrade, verify that default static accounts have been replaced with properly configured, unique passwords
- Confirm administrator access works with the new credentials
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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 $3,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3446 — 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-3446 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