dbcve.org
Nx OsOperating system · Cisco

CVE-2018-0330

HIGH · 8.8 CVSS v3.0 Published 2018-06-20
Fix available
A fix is available. Upgrade to 7.0 / 7.3 or later.
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 management application programming interface (API) in devices running, or based on, Cisco NX-OS Software could allow an authenticated, remote attacker to execute commands with elevated privileges. The vulnerability is due to a failure to properly validate certain parameters included within an NX-API request. An attacker that can successfully authenticate to the NX-API could submit a request designed to bypass NX-OS role assignment. A successful exploit could allow the attacker to execute commands with elevated privileges. This vulnerability affects the following if configured to use the NX-API feature: MDS 9000 Series Multilayer Switches, Nexus 2000 Series Switches, 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. Cisco Bug IDs: CSCvc73177, CSCve40903, CSCve40911.

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 Cisco NX-API management API allows authenticated attackers to execute commands with elevated privileges due to improper validation of certain parameters in NX-API requests. Attackers who can authenticate to NX-API can submit requests that bypass NX-OS role assignment, enabling privilege escalation.

MitigationApply the relevant Cisco security updates for NX-OS software. If patches are unavailable, restrict NX-API access to trusted management networks or disable NX-API if not required.

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.3, < 7.3\(3\)n1\(1\)= 6.0= 7.0= 7.1= 7.2>= 7.3, < 7.3.2d1>= 8.1, < 8.1.2= 6.2= 8.0= 8.2< 7.0\(3\)i3>= 7.0\(3\)i4, < 7.0\(3\)i7\(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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 is enabled
    Run 'show nxapi' or check the running configuration for 'nx-api' under the management interface or global configuration
    Affected if NX-API is enabled and the device version falls within the affected ranges listed in the CVE
  2. Identify the NX-OS version
    Run 'show version' and locate the 'NX-OS' or 'system: version' line in the output
    Affected if The version matches any of the affected versions: 6.0, 6.2, 7.0, 7.1, 7.2, 7.3 through 7.3.2d1 (excluding 7.3(3)n1(1)), 8.0, 8.2, 8.1 through 8.1.2, 7.0(3)i4 through 7.0(3)i7(1), or versions prior to 7.0(3)i3
  3. Verify NX-API authentication settings
    Run 'show running-config | include nx-api' to review NX-API configuration including authentication method and role mappings
    Affected if NX-API is configured with local authentication or any role that permits API access for the attacker

The device is affected if NX-API is enabled and the NX-OS version matches any of the vulnerable versions listed in the CVE, allowing an authenticated user to potentially escalate privileges through NX-API parameter manipulation.

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 7.0 / 7.3 / 7.3.2d1 or later
Fixed in 7.07.37.3.2d1
Interim mitigation

Apply the relevant Cisco security updates for NX-OS software. If patches are unavailable, restrict NX-API access to trusted management networks or disable NX-API if not required.

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