Sign inStart freeBook a demo

What is CVE-2019-1965?A high-severity flaw in NX-OS, explained.

High severity87 affected products
The short answer

CVE-2019-1965 is a high-severity flaw (CVSS 7.7) in NX-OS from Cisco, published on 28 August 2019. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.5%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 28 August 2019. Record last updated 16 October 2020. We keep this page's data up to date.

What it does

What is CVE-2019-1965? In plain terms.

It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.

The official description

A vulnerability in the Virtual Shell (VSH) session management for Cisco NX-OS Software could allow an authenticated, remote attacker to cause a VSH process to fail to delete upon termination. This can lead to a build-up of VSH processes that overtime can deplete system memory. When there is no system memory available, this can cause unexpected system behaviors and crashes. The vulnerability is due to the VSH process not being properly deleted when a remote management connection to the device is disconnected. An attacker could exploit this vulnerability by repeatedly performing a remote management connection to the device and terminating the connection in an unexpected manner. A successful exploit could allow the attacker to cause the VSH processes to fail to delete, which can lead to a system-wide denial of service (DoS) condition. The attacker must have valid user credentials to log in to the device using the remote management connection.

What kind of flaw is it?

  • CWE-400Uncontrolled Resource Consumption
  • CWE-772Missing Release of Resource after Effective Lifetime
CVSS 3.1 scoreHigh · 7.7

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn ordinary user account
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan take it offline

Severity vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

Exploitation

Is CVE-2019-1965 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.5%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days1.5%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
46out of 100Medium

CVE-2019-1965 scores 46. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2019-1965 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2019-1965? 87 products.

The published record lists 87 products from 1 vendor. Versions are shown as published: "before 7.1(5)n1(1b)" means every version up to, but not including, 7.1(5)n1(1b). If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2019-1965? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

1 link
Precursor Intelligence

Does CVE-2019-1965 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2019-1965 is a high-severity flaw in NX-OS from Cisco, published on 28 August 2019. It can be attacked from anywhere on the internet with an ordinary user account, and nobody has to click anything. If it works, the attacker can take it offline.

It scores 7.7 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2019-1965 is 46 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.5%. That can change at any time, which is why we keep watching.

For NX-OS from Cisco: before 7.1(5)n1(1b), before 6.2(22), before 7.0(3)i4(9), before 3.2(3k), 4.0 to before 4.0(2e), 5.2 to before 6.2(29) and 1 more. The record lists 87 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring