Asr 5000 Series SoftwareApplication · Cisco
CVE-2015-4201
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 Gateway General Packet Radio Service Support Node (GGSN) component on Cisco ASR 5000 devices with software 17.2.0.59184 and 18.0.L0.59219 allows remote attackers to cause a denial of service (Session Manager restart) via an invalid TCP/IP header, aka Bug ID CSCut68058.
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 GGSN component on Cisco ASR 5000 devices running software versions 17.2.0.59184 and 18.0.L0.59219 contains a vulnerability where processing invalid TCP/IP headers causes the Session Manager to restart, resulting in denial of service. An unauthenticated remote attacker can trigger this condition by sending specially crafted packets with malformed TCP/IP headers.
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
= 17.2.0.59184= 18.0.l059219CVSS 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 modelCheck if the device is a Cisco ASR 5000 Series router. Use 'show hardware' or 'show chassis' CLI command to confirm the model.Affected if Device is not a Cisco ASR 5000 Series (not affected)
-
Check the software versionRun 'show version' or 'show software' in the CLI to retrieve the installed software version number.Affected if Version is exactly 17.2.0.59184 or 18.0.L0.59219 (vulnerable)
-
Verify GGSN is configuredRun 'show ggsn service' or 'show ggsn' to check if the GGSN (Gateway GPRS Support Node) feature is enabled on the system.Affected if GGSN service is not configured or not running (not affected, since vulnerability is in GGSN component)
-
Confirm network exposureReview the network configuration to determine if the GGSN interface is directly accessible from untrusted networks. Use 'show ip interface' or 'show running-config' to inspect interface bindings.Affected if GGSN interface is exposed to untrusted networks (remotely exploitable)
The system is affected only if it is a Cisco ASR 5000 running exactly version 17.2.0.59184 or 18.0.L0.59219, has GGSN configured, and the GGSN interface is network-accessible to attackers.
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 fix for bug ID CSCut68058, which typically involves upgrading to a patched software version. Coordinate maintenance windows with carrier operations due to the service-impacting nature of the Session Manager restart.
Fix this in Asr 5000 Series Software
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.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,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4201 — 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-4201 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