Nx OsOperating system · Cisco

CVE-2019-1767

MEDIUM · 6.7 CVSS v3.1 Published 2019-05-15
Fix available
A fix is available. Upgrade to 8.3 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 implementation of a specific CLI command for Cisco NX-OS Software could allow an authenticated, local attacker with administrator credentials to cause a buffer overflow condition or perform command injection. This could allow the attacker to execute arbitrary commands with elevated privileges on the underlying operating system of an affected device. The vulnerability is due to insufficient validation of arguments passed to a certain CLI command. An attacker could exploit this vulnerability by including malicious input as the argument of the affected CLI command. A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system with root privileges. An attacker would need valid administrator credentials to exploit these vulnerabilities. NX-OS versions prior to 8.3(1) are affected.

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 confidence

A vulnerability in the Cisco NX-OS CLI command parser allows an authenticated administrator to cause buffer overflow or command injection due to insufficient input validation of CLI command arguments. Successful exploitation enables arbitrary command execution with root privileges on the affected device.

MitigationUpgrade Cisco NX-OS to version 8.3(1) or later to patch the vulnerability. Alternatively, restrict administrative access and monitor for suspicious CLI usage.

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.3\(1\)

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. Check Cisco NX-OS version
    Execute 'show version' or 'show system uptime' command in the NX-OS CLI to retrieve the installed software version
    Affected if The displayed version is earlier than 8.3(1)
  2. Confirm administrative CLI access exists
    Verify that the device is accessible via CLI and that administrator accounts are configured and reachable
    Affected if Authenticated administrator access to the CLI is possible, as the vulnerability requires an authenticated administrator session to exploit
  3. Review system logs for anomalous CLI commands
    Execute 'show logging log' or review syslog/smart call home logs for unexpected or malformed CLI command patterns
    Affected if Logs contain unusual command strings, buffer overflow patterns, or commands that were not issued by legitimate administrators
  4. Audit recent command history
    Use 'show history' or review accounting logs for recent CLI commands executed by administrators
    Affected if Command history shows unfamiliar commands or patterns indicative of injection or unauthorized execution

A system is affected if it runs Cisco NX-OS version earlier than 8.3(1) and has authenticated administrator access to the CLI, as the vulnerability resides in the CLI parser itself.

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 8.3 or later
Fixed in 8.3
Interim mitigation

Upgrade Cisco NX-OS to version 8.3(1) or later to patch the vulnerability. Alternatively, restrict administrative access and monitor for suspicious CLI usage.

Fix this in Nx Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1767 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