CVE-2020-3566
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 Distance Vector Multicast Routing Protocol (DVMRP) feature of Cisco IOS XR Software could allow an unauthenticated, remote attacker to exhaust process memory of an affected device. The vulnerability is due to insufficient queue management for Internet Group Management Protocol (IGMP) packets. An attacker could exploit this vulnerability by sending crafted IGMP traffic to an affected device. A successful exploit could allow the attacker to cause memory exhaustion, resulting in instability of other processes. These processes may include, but are not limited to, interior and exterior routing protocols. Cisco will release software updates that address this vulnerability.
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 confidenceThis vulnerability exists in Cisco IOS XR Software's Distance Vector Multicast Routing Protocol (DVMRP) feature. The root cause is insufficient queue management for Internet Group Management Protocol (IGMP) packets. An unauthenticated remote attacker can send specially crafted IGMP traffic to exhaust the process memory on the affected device, causing instability in critical processes including interior and exterior routing protocols.
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= 6.4.2CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 the device OSRun 'show version' or check the system banner to confirm the device runs Cisco IOS XR softwareAffected if The device is not running Cisco IOS XR, then this CVE does not apply
-
Check the IOS XR versionExecute 'show version' and locate the software version string (e.g., 6.4.2)Affected if The installed version matches exactly 6.4.2 (or falls within the affected range if broader ranges are published by Cisco)
-
Verify DVMRP feature statusRun 'show dvmrp interface' or 'show ip dvmrp interface' to check if DVMRP is enabled on any interfacesAffected if DVMRP is actively running on one or more interfaces - this is the vulnerable component
-
Confirm IGMP configurationExecute 'show igmp interface' to see if IGMP is configured and runningAffected if IGMP is enabled - the vulnerability stems from insufficient handling of IGMP packets within DVMRP
-
Monitor for memory exhaustionRun 'show process memory' or 'show memory' to check for abnormally high memory usage in routing processes, particularly the DVMRP or IGMP-related processesAffected if Memory usage for DVMRP/IGMP processes is unusually high or continuously growing, indicating potential exploitation
A user is affected if the device runs Cisco IOS XR version 6.4.2, has DVMRP enabled, and is processing IGMP traffic that could trigger memory exhaustion in the DVMRP process.
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 dataApply the Cisco software update when available. In the interim, filter or rate-limit IGMP traffic from untrusted sources at network borders to reduce exposure to unauthenticated attackers.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3566 — 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-2020-3566 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