dbcve.org
Nx OsOperating system · Cisco

CVE-2019-1776

MEDIUM · 6.7 CVSS v3.1 Published 2019-05-15
Fix available
A fix is available. Upgrade to 4.0 / 6.0 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
A vulnerability in the CLI of Cisco NX-OS Software could allow an authenticated, local attacker to execute arbitrary commands on the underlying Linux operating system with a privilege level of root. The vulnerability is due to insufficient validation of arguments passed to a specific CLI command on the affected device. An attacker could exploit this vulnerability by including malicious input as the argument of an affected command. A successful exploit could allow the attacker to execute arbitrary commands on the underlying Linux operating system with elevated privileges. An attacker would need valid administrator credentials to exploit this vulnerability.

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 NX-OS Software contains a vulnerability in its CLI where insufficient validation of arguments passed to a specific CLI command allows an authenticated local attacker with administrator credentials to execute arbitrary Linux commands with root privileges. The attack requires valid admin credentials and local access to the device CLI.

MitigationApply the relevant Cisco security patch for NX-OS when available. Until then, restrict administrative access to trusted personnel only and monitor CLI command usage for anomalies.

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
Nx OsOperating system
Affected:< 8.2\(2\)>= 8.3, < 8.3\(1\)< 7.0\(3\)i4\(9\)>= 7.0\(3\)i7, < 7.3\(3\)i7\(4\)< 6.0\(2\)a8\(11\)>= 7.0\(3\)i4, < 7.0\(3\)i4\(9\)>= 7.0\(3\), < 7.0\(3\)f3\(5\)< 7.3\(5\)n1\(1\)< 7.3\(3\)d1\(1\)>= 8.0, < 8.2\(2\)< 4.0\(1a\)

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. Determine the installed NX-OS version
    Run 'show version' from the NX-OS CLI to obtain the exact software version number
    Affected if The installed version falls within the affected ranges: < 8.2(2), >= 8.3 and < 8.3(1), < 7.0(3)i4(9), >= 7.0(3)i7 and < 7.3(3)i7(4), < 6.0(2)a8(11), >= 7.0(3)i4 and < 7.0(3)i4(9), >= 7.0(3) and < 7.0(3)f3(5), < 7.3(5)n1(1), < 7.3(3)d1(1), >= 8.0 and < 8.2(2), or < 4.0(1a)
  2. Verify if local CLI administrative accounts exist
    Use 'show user-account' or 'show running-config | include username' to list locally configured administrative accounts
    Affected if Local administrative accounts are configured, providing a potential attack vector for authenticated exploitation
  3. Confirm administrative access methods
    Review the NX-OS configuration for VSH (Virtual Shell) access methods using 'show running-config | include line|vty|console'
    Affected if Local console or VTY lines permit access, allowing an attacker with valid credentials to reach the CLI

Your environment is affected if the installed NX-OS version matches any of the vulnerable version ranges AND local administrative CLI access is possible.

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.

From vendor data
Upgrade available Upgrade to 4.0 / 6.0 / 7.0 or later
Fixed in 4.06.07.0
Interim mitigation

Apply the relevant Cisco security patch for NX-OS when available. Until then, restrict administrative access to trusted personnel only and monitor CLI command usage for anomalies.

Fix this in Nx Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1776 — 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-2019-1776 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