dbcve.org
Nx OsOperating system · Cisco

CVE-2018-0313

HIGH · 8.8 CVSS v3.1 Published 2018-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 NX-API feature of Cisco NX-OS Software could allow an authenticated, remote attacker to send a malicious packet to the management interface on an affected system and execute a command-injection exploit. The vulnerability is due to incorrect input validation of user-supplied data to the NX-API subsystem. An attacker could exploit this vulnerability by sending a malicious HTTP or HTTPS packet to the management interface of an affected system that has the NX-API feature enabled. A successful exploit could allow the attacker to execute arbitrary commands with root privileges. Note: NX-API is disabled by default. This vulnerability affects MDS 9000 Series Multilayer Switches, Nexus 2000 Series Fabric Extenders, Nexus 3000 Series Switches, Nexus 3500 Platform Switches, Nexus 5500 Platform Switches, Nexus 5600 Platform Switches, Nexus 6000 Series Switches, Nexus 7000 Series Switches, Nexus 7700 Series Switches, Nexus 9000 Series Switches in standalone NX-OS mode, Nexus 9500 R-Series Line Cards and Fabric Modules. Cisco Bug IDs: CSCvd47415, CSCve03216, CSCve03224, CSCve03234.

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

The NX-API feature in Cisco NX-OS software contains a command injection vulnerability due to insufficient input validation of user-supplied data. An authenticated attacker can send malicious HTTP/HTTPS packets to the management interface of affected systems with NX-API enabled, allowing execution of arbitrary commands with root privileges.

MitigationIf NX-API is not required, ensure it remains disabled. If enabled, apply the appropriate Cisco patches for CSCvd47415/CSCve03216/CSCve03224/CSCve03234. Verify all management access uses proper authentication and consider network segmentation of management interfaces.

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:= 7.0\(0\)hsk\(0.357\)= 8.0\(1\)s20= 8.1\(0\)bd\(0.20\)= 8.1\(0.97\)s0= 8.1\(1\)s5all versions

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm NX-API feature status
    Run the command 'show feature | include nxapi' on the Cisco NX-OS device CLI to check if NX-API is enabled. If the output shows 'nxapi' with a status of 'enabled', the feature is active.
    Affected if NX-API is enabled on the device (status shows 'enabled' or '1')
  2. Check NX-OS software version
    Run the command 'show version' on the Cisco NX-OS device CLI and locate the version string in the output. Compare your installed version against the affected versions: 7.0(0)hsk(0.357), 8.0(1)s20, 8.1(0)bd(0.20), 8.1(0.97)s0, 8.1(1)s5, or any version that matches the pattern of these branches.
    Affected if The installed NX-OS version matches one of the affected versions or falls within the vulnerable version branches (7.0, 8.0, 8.1 series as listed)
  3. Verify NX-API management interface configuration
    Run the command 'show running-config | include nxapi' to review the NX-API configuration, including whether the management interface is configured to accept HTTP/HTTPS connections.
    Affected if NX-API is configured and bound to an accessible management interface (HTTP or HTTPS is enabled)
  4. Confirm management access authentication
    Review the NX-API configuration using 'show running-config' to verify that authentication is properly configured for NX-API access.
    Affected if NX-API is enabled and accessible without proper authentication enforcement (authentication is weak or misconfigured)

The environment is affected if NX-API is enabled AND the NX-OS version matches one of the affected versions listed in the CVE, making the device vulnerable to authenticated command injection via malicious HTTP/HTTPS requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If NX-API is not required, ensure it remains disabled. If enabled, apply the appropriate Cisco patches for CSCvd47415/CSCve03216/CSCve03224/CSCve03234. Verify all management access uses proper authentication and consider network segmentation of management interfaces.

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 help mitigating

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-2018-0313 — 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-2018-0313 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