CVE-2019-1610
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 the CLI of Cisco NX-OS Software could allow an authenticated, local attacker to execute arbitrary commands on the underlying operating system of an affected device. The vulnerability is due to insufficient validation of arguments passed to certain CLI commands. 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 operating system with elevated privileges. An attacker would need valid administrator credentials to exploit this vulnerability. Nexus 3500 Platform Switches and Nexus 3000 Series Switches software versions prior to 7.0(3)I7(4) 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 confidenceA command injection vulnerability in Cisco NX-OS CLI allows an authenticated local attacker with administrator credentials to execute arbitrary commands on the underlying operating system with elevated privileges. The flaw is due to insufficient validation of arguments passed to certain CLI commands, allowing malicious input to be injected.
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>= 7.0\(3\), <= 7.0\(3\)i7\(4\)< 7.0\(3\)i7\(4\)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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelRun 'show module' or 'show inventory' from the NX-OS CLI to confirm the hardware is a Nexus 3000 or Nexus 3500 Series switchAffected if The device is NOT a Nexus 3000 or Nexus 3500 series switch - different models are not affected by this specific vulnerability
-
Check the NX-OS software versionRun 'show version' from the NX-OS CLI and locate the 'NXOS' or 'system: version' line showing the exact version numberAffected if The running NX-OS version is 7.0(3) through 7.0(3)I7(4) inclusive - versions lower than 7.0(3) and versions 7.0(3)I7(4) and later are not affected
-
Verify the specific version falls within the affected rangeCompare your installed version to the affected range: versions >= 7.0(3) and < 7.0(3)I7(4) are vulnerable. Note that version 7.0(3)I7(4) itself is not affectedAffected if The version is 7.0(3)I1(1), 7.0(3)I2(1), 7.0(3)I3(1), 7.0(3)I4(1), 7.0(3)I5(1), 7.0(3)I6(1), 7.0(3)I7(1), 7.0(3)I7(2), 7.0(3)I7(3), or 7.0(3)I7(4) - these are in the vulnerable range
You are affected if your device is a Nexus 3000 or Nexus 3500 series switch running NX-OS version 7.0(3) through 7.0(3)I7(4) and an attacker can obtain valid administrator credentials to access the CLI.
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.
From vendor data7.0
Upgrade Cisco NX-OS to version 7.0(3)I7(4) or later on affected Nexus 3500 and Nexus 3000 Series switches. This is a local authenticated attack requiring valid administrator credentials.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1610 — 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-2019-1610 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