Ios XrOperating system · Cisco
CVE-2013-6700
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 SNMP module in Cisco IOS XR allows remote attackers to cause a denial of service (process reload) via a request for an unspecified MIB, aka Bug ID CSCuh43144.
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 · moderate confidenceThe SNMP module in Cisco IOS XR contains a vulnerability where a remote attacker can cause a denial of service by sending a specially crafted SNMP request for an unspecified MIB. This causes the affected process to reload, resulting in service disruption.
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 OSExecute 'show version' or check the device prompt to confirm the device runs Cisco IOS XRAffected if The device does not run Cisco IOS XR (this CVE does not apply)
-
Check if SNMP is globally enabledRun 'show snmp' or 'show running-config | include snmp' in IOS XR to see if SNMP is configured and enabledAffected if SNMP is enabled and running (the vulnerability is present when SNMP is active)
-
Verify SNMP community string configurationRun 'show snmp community' to see configured community strings and their access permissionsAffected if SNMP community strings are configured with read/write access (vulnerable to exploitation)
-
Check SNMP access controlRun 'show snmp access-list' or examine the SNMP configuration for ACL bindings that restrict SNMP accessAffected if SNMP is accessible from untrusted networks or no ACL is applied (exposed to remote attack)
-
Determine SNMP exposureReview the interface configurations and management plane access settings to determine if SNMP ports (161/UDP, 162/UDP) are reachable from outside trusted networksAffected if SNMP service is reachable from untrusted or external network segments
A Cisco IOS XR device is affected by this CVE if SNMP is enabled and accessible from a network where an attacker could send malicious SNMP requests.
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 patch for IOS XR addressing CSCuh43144. If no patch is available, restrict SNMP access through ACLs or disable SNMP if not required.
Fix this in Ios Xr
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6700 — 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-6700 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