Ios XrOperating system · Cisco
CVE-2019-1712
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 · uneditedA vulnerability in the Protocol Independent Multicast (PIM) feature of Cisco IOS XR Software could allow an unauthenticated, remote attacker to cause the PIM process to restart, resulting in a denial of service condition on an affected device. The vulnerability is due to the incorrect processing of crafted AutoRP packets. An attacker could exploit this vulnerability by sending crafted packets to port UDP 496 on a reachable IP address on the device. A successful exploit could allow the attacker to cause the PIM process to restart. Software versions prior to 6.2.3, 6.3.2, 6.4.0, and 6.5.1 are affected.
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 confidenceA vulnerability in the Protocol Independent Multicast (PIM) feature of Cisco IOS XR Software allows an unauthenticated, remote attacker to cause denial of service by sending crafted AutoRP packets to UDP port 496 on an affected device. The vulnerability is due to incorrect processing of these crafted packets, causing the PIM process to restart.
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
Ios XrOperating system
< 6.2.3>= 6.2.25, < 6.3.2>= 6.3.3, < 6.4.0>= 6.4.1, < 6.5.1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco IOS XR versionExecute 'show version' or 'admin show version' on the IOS XR device to obtain the running software versionAffected if The displayed version falls within any of these ranges: < 6.2.3, >= 6.2.25 and < 6.3.2, >= 6.3.3 and < 6.4.0, or >= 6.4.1 and < 6.5.1
-
Verify PIM feature is enabledExecute 'show pim interface' or check the running configuration for 'router pim' commands to determine if Protocol Independent Multicast is configuredAffected if PIM is enabled and the device is running a vulnerable IOS XR version from step 1
-
Confirm UDP port 496 accessibilityCheck if UDP port 496 is open on the device by reviewing access control lists, interface configurations, or using 'show udp ports' commandAffected if UDP port 496 is reachable from untrusted networks and the device meets the vulnerable conditions from steps 1 and 2
A device is affected if it runs a vulnerable Cisco IOS XR version (6.2.3 > version < 6.5.1 with the specific gaps noted), has PIM enabled, and has UDP port 496 exposed to untrusted network traffic.
Generated from the published advisory. Verify against your own configuration.
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 data6.2.36.3.26.4.0
Upgrade Cisco IOS XR Software to version 6.2.3, 6.3.2, 6.4.0, 6.5.1 or later. Additionally, filter inbound UDP port 496 traffic at network perimeter as a compensating control.
Fix this in Ios Xr
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1712 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-1712 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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