Ios XrOperating system · Cisco
CVE-2013-3470
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 · uneditedThe RIP process in Cisco IOS XR allows remote attackers to cause a denial of service (process crash) via a crafted version-2 RIP packet, aka Bug ID CSCue46731.
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 confidenceThe RIP (Routing Information Protocol) process in Cisco IOS XR contains a vulnerability where a remote attacker can send a specially crafted RIP version-2 packet to cause the RIP process to crash, resulting in denial of service. The vulnerability is triggered by malformed packets that the IOS XR RIP implementation fails to handle properly.
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
all versionsCVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 OS and confirm IOS XRRun 'show version' or check the system banner to confirm the device runs Cisco IOS XR. This CVE affects all versions of IOS XR.Affected if The device is running any version of Cisco IOS XR.
-
Check if RIP is enabledRun 'show rip' or 'show rip database' in IOS XR EXEC mode to check if the RIP process is running and configured.Affected if RIP process is active or configured on the device.
-
Identify RIP-enabled interfacesRun 'show rip interface' or review the running configuration for 'router rip' and 'network' statements under RIP configuration mode.Affected if RIP is enabled on any interface and is actively receiving or processing RIP packets.
-
Check RIP version in useRun 'show rip' or examine the RIP configuration for 'version 2' settings. The vulnerability specifically affects RIP version-2 packet handling.Affected if RIP version 2 is configured or in use (default for most IOS XR RIP configurations).
-
Look for RIP process crashes or instabilityRun 'show log' or 'show logging' to search for recent RIP process crashes, resets, or error messages related to RIP packet processing.Affected if There are recent RIP process crashes or errors logged, especially after receiving packets from untrusted sources.
If the device runs Cisco IOS XR with RIP version 2 enabled on any interface and receives RIP packets from untrusted networks, it is vulnerable to this denial-of-service flaw.
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 Cisco IOS XR security updates when available. Until patches can be deployed, implement ingress filtering or ACLs at network boundaries to block unauthorized RIP packets from untrusted sources, and disable RIP on interfaces that do not require it.
Fix this in Ios Xr
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3470 — 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-2013-3470 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