dbcve.org
Asr 5000 SoftwareApplication · Cisco

CVE-2016-1436

HIGH · 7.5 CVSS v3.0 Published 2016-06-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The General Packet Radio Switching Tunneling Protocol 1 (aka GTPv1) implementation on Cisco ASR 5000 Packet Data Network Gateway devices before 19.4 allows remote attackers to cause a denial of service (Session Manager process restart) via a crafted GTPv1 packet, aka Bug ID CSCuz46198.

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 confidence

The Cisco ASR 5000 Packet Data Network Gateway contains a vulnerability in its GTPv1 (General Packet Radio Switching Tunneling Protocol 1) implementation. Remote attackers can send a specially crafted GTPv1 packet to trigger a denial of service condition that causes the Session Manager process to restart, disrupting packet gateway services.

MitigationUpgrade Cisco ASR 5000 devices to software version 19.4 or later to patch this vulnerability. During the upgrade, coordinate a maintenance window to minimize service impact.

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 SoftwareApplication
Affected:= 17.2.0= 17.2.0.59184= 17.3.1= 17.7.0= 18.0.0= 18.0.0.57828= 18.0.0.59167= 18.0.0.59211= 18.0.l0.59219= 18.1.0= 18.1.0.59776= 18.1.0.59780

CVSS 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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify device model is Cisco ASR 5000
    Execute 'show hardware' or 'show version' CLI command and confirm the model number in the output displays ASR 5000
    Affected if The device model is not Cisco ASR 5000 (this CVE only applies to ASR 5000 series)
  2. Check installed software version
    Execute 'show version' CLI command and locate the software version string in the output
    Affected if The installed version matches any of these: 17.2.0, 17.2.0.59184, 17.3.1, 17.7.0, 18.0.0, 18.0.0.57828, 18.0.0.59167, 18.0.0.59211, 18.0.0.59219, 18.1.0, 18.1.0.59776, or 18.1.0.59780
  3. Confirm GTPv1 protocol is enabled
    Execute 'show gtp statistics' or 'show gtp service' CLI command to verify GTPv1 is configured and active on the system
    Affected if GTPv1 is enabled and the software version matches the affected list (the vulnerability only triggers when GTPv1 processing is active)

The environment is affected if the device is a Cisco ASR 5000 running any of the listed versions with GTPv1 protocol enabled and processing traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Cisco ASR 5000 devices to software version 19.4 or later to patch this vulnerability. During the upgrade, coordinate a maintenance window to minimize service impact.

Fix this in Asr 5000 Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1436 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1436 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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