dbcve.org
Nx OsOperating system · Cisco

CVE-2019-1963

MEDIUM · 6.5 CVSS v3.0 Published 2019-08-28
Fix available
A fix is available. Upgrade to 2.2.2.91 / 2.3.1.130 or later.
See remediation →
71/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
A vulnerability in the Simple Network Management Protocol (SNMP) input packet processor of Cisco FXOS Software and Cisco NX-OS Software could allow an authenticated, remote attacker to cause the SNMP application on an affected device to restart unexpectedly. The vulnerability is due to improper validation of Abstract Syntax Notation One (ASN.1)-encoded variables in SNMP packets. An attacker could exploit this vulnerability by sending a crafted SNMP packet to the SNMP daemon on the affected device. A successful exploit could allow the attacker to cause the SNMP application to restart multiple times, leading to a system-level restart and a denial of service (DoS) condition.

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 SNMP input packet processor of Cisco FXOS and NX-OS software allows an authenticated remote attacker to cause unexpected SNMP application restarts due to improper validation of ASN.1-encoded variables in SNMP packets. Repeated exploitation can lead to system-level restart and DoS condition.

MitigationApply Cisco security updates for FXOS and NX-OS software; until patched, restrict SNMP access to trusted management networks/hosts and consider disabling SNMP 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:>= 5.2, < 6.2\(29\)>= 7.3, < 8.4< 13.2\(7k\)>= 14.0, < 14.0\(2c\)>= 14.1, < 14.1\(1i\)>= 7.0\(3\)f, < 9.2\(3\)< 7.1\(5\)n1\(1b\)>= 7.3, < 7.3\(5\)n1\(1\)< 6.2\(22\)>= 7.2, < 7.2\(0\)d1\(1\)>= 8.0, < 8.2\(3\)>= 8.3, < 8.3\(2\)
Fx OsOperating system
Affected:< 2.2.2.91>= 2.3, < 2.3.1.130>= 2.4, < 2.4.1.222

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify the NX-OS version
    Run 'show version' on the device CLI and locate the NX-OS software version number (for example, 7.0(3)I7(3))
    Affected if The installed version falls within any of the following ranges: >= 5.2 < 6.2(29); >= 7.3 < 8.4; < 13.2(7k); >= 14.0 < 14.0(2c); >= 14.1 < 14.1(1i); >= 7.0(3)F < 9.2(3); < 7.1(5)N1(1b); >= 7.3 < 7.3(5)N1(1); < 6.2(22); >= 7.2 < 7.2(0)N1(1); >= 8.0 < 8.2(3); >= 8.3 < 8.3(2)
  2. Identify the FXOS version
    Run 'show version' on the device CLI and locate the FXOS software version number
    Affected if The installed version is less than 2.2.2.91, or >= 2.3 and less than 2.3.1.130, or >= 2.4 and less than 2.4.1.222
  3. Verify SNMP is enabled
    Run 'show snmp' and confirm the SNMP engine status shows it is enabled and running
    Affected if SNMP is actively enabled on the device (the vulnerability requires SNMP to be processed, so SNMP must be running)
  4. Check SNMP configuration details
    Run 'show snmp community' and 'show snmp group' to see configured community strings and SNMP user/group associations
    Affected if Any SNMP community or user is configured (the CVE states an authenticated attacker with SNMP credentials can exploit this)

The device is affected if it runs Cisco NX-OS or FXOS within the specified version ranges AND has SNMP enabled with configured authentication credentials.

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 2.2.2.91 / 2.3.1.130 / 2.4.1.222 or later
Fixed in 2.2.2.912.3.1.1302.4.1.222
Interim mitigation

Apply Cisco security updates for FXOS and NX-OS software; until patched, restrict SNMP access to trusted management networks/hosts and consider disabling SNMP if not required.

Fix this in Nx Os Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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