Asr 5000 Series SoftwareApplication · Cisco
CVE-2015-0617
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 · uneditedCisco ASR 5500 System Architecture Evolution (SAE) Gateway devices allow remote attackers to cause a denial of service (CPU consumption and SNMP outage) via malformed SNMP packets, aka Bug ID CSCur13393.
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 confidenceCisco ASR 5500 System Architecture Evolution (SAE) Gateway devices contain a vulnerability in SNMP packet processing. Remote unauthenticated attackers can send malformed SNMP packets to trigger excessive CPU consumption and complete SNMP service outage, resulting in denial of service.
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
Asr 5000 Series SoftwareApplication
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 device modelRun 'show version' or check the device hardware label to confirm the platform is a Cisco ASR 5000 or ASR 5500 Series GatewayAffected if Device is a Cisco ASR 5000 or ASR 5500 series platform
-
Verify SNMP is enabledRun 'show snmp' or 'show running-config | include snmp' to check if SNMP is configured and enabled on the deviceAffected if SNMP is configured and enabled (any SNMP community strings or users are defined)
-
Confirm software versionRun 'show version' and note the installed software release version numberAffected if Any version of Cisco ASR 5000 Series Software is running (all versions are affected according to the advisory)
-
Check SNMP access controlReview SNMP access lists or ACLs applied to SNMP with 'show access-lists' or inspect the SNMP configuration for any access restrictionsAffected if SNMP is exposed to untrusted networks (no ACL or restrictive access list is applied to SNMP)
-
Verify SNMP service statusRun 'show snmp statistics' to check current SNMP service health and CPU impact from recent SNMP packetsAffected if SNMP service is running and accessible
If the device is a Cisco ASR 5000/5500 series with SNMP enabled and exposed to untrusted networks, the environment is affected by this vulnerability.
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 bug ID CSCur13393. If immediate patching is not feasible, restrict SNMP access to trusted management networks using ACLs or consider disabling SNMP if not operationally required.
Fix this in Asr 5000 Series Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0617 — 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-2015-0617 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