Asr 5000 Series SoftwareApplication · Cisco
CVE-2015-4275
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 Packet Data Network Gateway (aka PGW) component on Cisco ASR 5000 devices with software 18.0.0.59167 and 18.0.0.59211 allows remote attackers to cause a denial of service via a malformed header in a GTPv2 packet, aka Bug ID CSCut11534.
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 confidenceDenial of service vulnerability in Cisco ASR 5000 Packet Data Network Gateway (PGW). Remote attackers can crash the device by sending GTPv2 packets with malformed headers. The vulnerability affects software versions 18.0.0.59167 and 18.0.0.59211 specifically. The attack requires network access to the GTPv2 interface and no authentication.
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
= 18.0.0.59167= 18.0.0.59211CVSS 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.
-
Check the installed Cisco ASR 5000 software versionLog into the device CLI and run the command 'show version' or 'show software' to display the installed software versionAffected if The version displayed is exactly 18.0.0.59167 or 18.0.0.59211
-
Confirm the PGW (Packet Data Network Gateway) feature is enabledRun 'show configuration' or 'show running-config' and look for PGW-related services or the 'pgw-service' command in the configurationAffected if PGW service is configured and enabled on the device
-
Verify GTPv2 protocol support is activeCheck the PGW configuration for GTPv2 bindings by running 'show pgw-service' or inspecting the GTPv2 interface bindings in the configurationAffected if GTPv2 interfaces are configured and active on the PGW
-
Assess GTPv2 interface network exposureReview the network configuration to determine if the GTPv2 interface (typically on S5/S8 or S2a interfaces) is accessible from external networks or untrusted zonesAffected if The GTPv2 interface is reachable from untrusted network segments without packet filtering
The device is affected if it runs version 18.0.0.59167 or 18.0.0.59211 AND has PGW with GTPv2 enabled AND the GTPv2 interface is network-accessible to untrusted parties.
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 software update/patch for Bug ID CSCut11534. Alternatively, implement GTPv2 packet filtering at network boundaries to drop malformed packets until the vendor patch can be applied.
Fix this in Asr 5000 Series Software
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-4275 — 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-4275 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