dbcve.org
Nexus DashboardApplication · Cisco

CVE-2022-20907

MEDIUM · 6.7 CVSS v3.1 Published 2022-07-22
Fix available
A fix is available. Upgrade to 2.2 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
Multiple vulnerabilities in Cisco Nexus Dashboard could allow an authenticated, local attacker to elevate privileges on an affected device. These vulnerabilities are due to insufficient input validation during CLI command execution on an affected device. An attacker could exploit these vulnerabilities by authenticating as the rescue-user and executing vulnerable CLI commands using a malicious payload. A successful exploit could allow the attacker to elevate privileges to root on an affected device.

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 confidence

Cisco Nexus Dashboard contains privilege escalation vulnerabilities where insufficient input validation during CLI command execution allows an authenticated attacker (as rescue-user) to inject malicious payloads and gain root privileges.

MitigationApply Cisco's official patch when available; in the meantime, restrict rescue-user account access and monitor CLI command execution for suspicious patterns.

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
Nexus DashboardApplication
Affected:>= 2.0, < 2.2\(1e\)

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Cisco Nexus Dashboard installed version
    Access the Nexus Dashboard admin UI or use the 'show version' command via CLI/ssh to determine the exact software version running
    Affected if The installed version falls within >= 2.0 and < 2.2(1e)
  2. Verify rescue-user account existence
    Check if the rescue-user account is configured on the Nexus Dashboard by reviewing local user accounts in the administration settings or via 'show user' CLI output
    Affected if The rescue-user account exists and is active on the system
  3. Confirm CLI access method availability
    Determine if CLI access is enabled by checking whether SSH or console access is permitted for the rescue-user account
    Affected if CLI access via SSH or console is available for the rescue-user account
  4. Review CLI command execution logs
    Examine CLI audit logs or command history for the rescue-user account, looking for any unexpected or suspicious command patterns that may indicate exploitation attempts
    Affected if Unusual or unauthorized CLI commands appear in the logs associated with the rescue-user account

You are affected if your Cisco Nexus Dashboard version is 2.0 or higher but below 2.2(1e) and the rescue-user account has active CLI access, allowing potential privilege escalation to root.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.2 or later
Fixed in 2.2
Interim mitigation

Apply Cisco's official patch when available; in the meantime, restrict rescue-user account access and monitor CLI command execution for suspicious patterns.

Recommended fix Moderate confidence

Upgrade to Cisco Nexus Dashboard version 2.2(1e) or later

  1. 1. Back up current Nexus Dashboard configuration and data.
  2. 2. Review Cisco Nexus Dashboard release notes for version 2.2(1e) or later to understand any changes or migration requirements.
  3. 3. Download the fixed version (2.2(1e) or later) from Cisco.com or your authorized Cisco support channel.
  4. 4. Follow Cisco's documented upgrade procedure for Nexus Dashboard, typically via the web UI or CLI.
  5. 5. After upgrade, verify the system is operational and test that the vulnerability is resolved.
  6. 6. Confirm the new version by running 'show version' or checking the web UI.
Caveat Review Cisco release notes for any configuration or compatibility changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nexus Dashboard Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,360
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20907 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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