dbcve.org
Nx OsOperating system · Cisco

CVE-2015-0686

MEDIUM · 6.3 CVSS v2.0 Published 2015-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
The SNMP implementation in Cisco NX-OS 6.1(2)I2(3) on Nexus 9000 devices, when a Reset High Availability (HA) policy is configured, allows remote authenticated users to cause a denial of service (device reload) via unspecified vectors, aka Bug ID CSCuq92240.

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

The SNMP implementation in Cisco NX-OS 6.1(2)I2(3) on Nexus 9000 switches contains a denial-of-service vulnerability triggered when a Reset High Availability (HA) policy is configured. An authenticated remote user sending certain unspecified SNMP packets can cause the device to unexpectedly reload, disrupting network services.

MitigationRestrict SNMP access to trusted management networks and limit authenticated user privileges. Upgrade to a patched NX-OS version when available from Cisco. During remediation, schedule a maintenance window as the device will likely need to be reloaded after the upgrade.

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:= 6.1\(2\)i2\(3\)

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
M
Authentication
Single
Confidentiality
None
Integrity
None
Availability
Complete

AV:N/AC:M/Au:S/C:N/I:N/A:C

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. Identify the device model
    Run 'show version' or 'show inventory' to confirm the device is a Cisco Nexus 9000 series switch
    Affected if Device is NOT a Nexus 9000 series switch - this CVE only applies to that platform
  2. Check the NX-OS version
    Run 'show version' and locate the 'NXOS' or 'system' version line. Compare it to the affected version 6.1(2)I2(3)
    Affected if Version is NOT exactly 6.1(2)I2(3) - only this specific version is affected
  3. Verify SNMP is enabled
    Run 'show snmp' to check if SNMP is configured and enabled on the device
    Affected if SNMP is disabled or not configured - the attacker needs SNMP access to exploit this
  4. Check for Reset HA policy configuration
    Run 'show ha policy' or 'show running-config | include ha' to determine if a Reset High Availability policy is configured
    Affected if No Reset HA policy is configured - the vulnerability is only triggered when this specific policy is in place

A user is affected only if they have a Nexus 9000 switch running exactly NX-OS version 6.1(2)I2(3) with SNMP enabled and a Reset HA policy configured.

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

Restrict SNMP access to trusted management networks and limit authenticated user privileges. Upgrade to a patched NX-OS version when available from Cisco. During remediation, schedule a maintenance window as the device will likely need to be reloaded after the upgrade.

Fix this in Nx Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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