CVE-2019-1968
No exploitation reported by the sources we read.
- Published2019-08-30
- WeaknessCWE-116 · CWE-20
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
A vulnerability in the NX-API feature of Cisco NX-OS Software could allow an unauthenticated, remote attacker to cause an NX-API system process to unexpectedly restart. The vulnerability is due to incorrect validation of the HTTP header of a request that is sent to the NX-API. An attacker could exploit this vulnerability by sending a crafted HTTP request to the NX-API on an affected device. A successful exploit could allow the attacker to cause a denial of service (DoS) condition in the NX-API service; however, the NX-OS device itself would still be available and passing network traffic. Note: The NX-API feature is disabled by default.
Timeline
dates in UTC- 2019-08-3009:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-1968?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-1968?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 7.3 | = 7.3 | no fix published | NVD |
| 8.1 | = 8.1 | no fix published | NVD |
| 8.2 | = 8.2 | no fix published | NVD |
| 8.3 | = 8.3 | no fix published | NVD |
| 6.1 | = 6.1\(2\)i2 | no fix published | NVD |
| 6.1 | = 6.1\(2\)i3 | no fix published | NVD |
| 7.0 | = 7.0\(3\)i4 | no fix published | NVD |
| 7.0 | = 7.0\(3\)i7 | no fix published | NVD |
| 9.2 | = 9.2 | no fix published | NVD |
| 6.0 | = 6.0\(2\)a8 | no fix published | NVD |
| 7.0 | = 7.0\(3\)f | no fix published | NVD |
| 7.1 | = 7.1 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
Advisories and patches
- tools.cisco.comVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Published
- 2019-08-30
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2019-1968?
Is CVE-2019-1968 actively exploited?
What is the CVSS score for CVE-2019-1968?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.