CVE-2019-1760 json
Cisco IOS XE Software Performance Routing Version 3 Denial of Service Vulnerability
published 7y ago modified 4mo ago also EUVD-2019-10317
- cvss
- 6.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
A vulnerability in Performance Routing Version 3 (PfRv3) of Cisco IOS XE Software could allow an unauthenticated, remote attacker to cause the affected device to reload. The vulnerability is due to the processing of malformed smart probe packets. An attacker could exploit this vulnerability by sending specially crafted smart probe packets at the affected device. A successful exploit could allow the attacker to reload the device, resulting in a denial of service (DoS) attack on an affected system.
Patch / fix
Is CVE-2019-1760 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
2.14% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.8 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H |
| NVD | 3.0 | 5.9 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.1 | AV:N/AC:M/Au:N/C:N/I:N/A:C |
Affected products
- Cisco Cisco IOS XE Software
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
tools.cisco.com
/security/center/content/CiscoSecurityAdvisory/cisco-sa-20190327-pfrv3
vendor-advisory, patch
-
securityfocus.com
/bid/107611
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2019-1760
- NVD CVE-2019-1760
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.